DavidA
I then closed and deleted the project in SmartSVN and then opened the working copy again. Now the 'History Scheduled' files are not shown at all by SmartSVN but look fine in TortoiseSVN. How can I show them again in SmartSVN? David
DavidA
Ok, my mistake, 'show unchanged files' was not selected. Now I can see the files and they are shown as 'Unchanged'. So the conclusion is that my move unexpectedly gave a result of 'History scheduled', which I resolved by deleting the SmartSVN project and re-opening the working copy. May I suggest that there is a bug that is causing unnecessary 'History scheduled' states, and that the documentation needs to be improved to explain how to deal with this state? Best regards David
Peter Pakos
Hi David, Files marked as History-Scheduled indicate that a parent directory has been added with history, which implicitly adds this file with history. This means that the file is not actually a new file, but actually a direct descendant of some other file in the Subversion repository. This means that the file cannot be committed (there should be no output in svn diff, since the file has not actually changed). If you were to make some local modifications to the file, they would appear in SmartSVN (and svn diff output). This is expected and svn command should behave in exactly the same way. I hope this helps.
DavidA
Hi Peter Thanks for your reply. But what is the user expected to do with a file marked 'History Scheduled'? Is it ok to leave it as it is or should some action be taken? I have just seen another instance of this. I renamed a parent folder and the states of the files in a folder under that renamed folder are now 'History scheduled'. You wrote 'svn command should behave in exactly the same way' but executing svn status on that folder shows nothing. Please will you explain what is the use of 'History scheduled' and what I should do about files marked with this state? BR David
Peter Pakos
Hi David, You don't have to do anything with these files. This status is only for informational purposes and it should change to 'unchanged' when you commit the directory rename/move. 'svn status' correctly shows nothing as there is no alteration as such to these files. I agree that it may be a bit confusing.
DavidA
Hi Peter The status did not change to 'unchanged' when I committed the directory rename/move. I am going to raise a bug report for this. BR David
DavidA
Hi Matheus I can't get the bug report link at the moment, but I believe the bug is fixed in SmartSVN 7.6.3. Best regards David
jmm
Similar issue in version 8.6.6 (build #3409) After a commit done by selecting the "root" of the project, I have one file in local state "History Scheduled". It might be caused by following: The file was completely replaced in the trunk of our project. Not only the content changed. The complete file was replaced for what reason ever. The name and the location is the same as before. After merging the trunk into my development branch the above described behaviour occures.
Ansjh
Hi, this is still an issue in 9.1.2 build #5050. After renaming a directory, I wasn't able to commit due to "History Scheduled" changes. Instead, I used the terminal to manually commit the directory deletion and rename (eg. "svn commit oldname newname"). After that, it still showed History Scheduled until I restarted SmartSVN.