Hello,
I was wandering what the right thing to do is in the following use case:
I am versioning / and I commit several revisions. Let's say HEAD is now
42. Then I want to go back to rev 23 and I want to have exactly the
state that my filesystem had, when I committed rev 23. After looking at
the situation and testing stuff, I want to go back to HEAD, ignoring all
changes that my testing might have caused to rev 23.
At the moment I do the following:
# / is at rev 42 with maybe some changes, so commit
fsvs commit -l "Bla"
# Update to rev 23
fsvs update -r 23
# Do some testing.
# Now back to HEAD
fsvs update
The last update can cause problems, when files were changed by my
activities. I then do an fsvs revert FILE, but there can be a lot of
changed files.
From a former mail on this list, I understood that revert is the
correct way to force an update on a locally modified file. So once
recursive revert is implemented, could I then use
fsvs revert /
instead of the last fsvs update? Or this there an option I could use to
update, which is ignores local modifications? Do you have any estimation
when recursive revert will be implemented?
I looked into your source code to see if I could code the recursive
revert myself, but my C skills are very limited... Fsvs is a great tool,
I appreciate the time and work you invest in this tool.
Best regards,
Simon
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
