Steve,
Usually what is done here is the incorrect commit is moved to a
different branch, which is typically hidden. This can be done using
"fossil amend". Then you update to the new head of your branch (the
previous commit) using "fossil update" and retry your commit.
It's also possible to shun the commit artifact on every system that has
learned of it (given that no new commits are based off it) and a rebuild
will drop the un-referenced data artifact. This is not recommended in the
normal case of a simple error being made, since you'll have to touch every
clone that has the commit artifact.
Thanks,
Roy Keene
On Wed, 16 Aug 2017, Steve Schow wrote:
I know the fossil paradigm generally frowns on the idea of undoing
commits. Please tell me your thoughts about the best approach to handle
the following situation.
a few file is added to the checkout and committed. So the commit has
one new file, nothing else. It is later determined that the entirely
wrong version of that file was committed for the first version of the
file and we?d like to back it out to do it properly?
Is that possible at all or if not, what is the best way to handle that
kind of situation with fossil?
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
