On 5/22/2016 2:10 PM, Steve Schow wrote:
> Is there currently any way in fossil to take a checkin and seperate
> one of the files in the checkin to a seperate checkin?
> 
> Sometimes I occasionally hit commit and after committing realize there
> was another unrelated file that I had added earlier for something
> entirely different.  So two files end up commited with the checkin,
> but really I would prefer if they had been seperate checkins.  Is
> there currently any way to clean this up after the fact?  To move one
> of the file changes to a different checkin?

You have two sensible options.  One, you could backout merge the
check-in then follow it up with what you intended in the first place.
Two, you could move the erroneous check-in to a branch, update to the
prior check-in, then commit as intended.  I usually do the latter,
naming the branch "mistake" and marking it as hidden and closed.

The third option is shunning.  Don't do that.  It's dangerous and far
more trouble than it's worth.

-- 
Andy Goth | <andrew.m.goth/at/gmail/dot/com>

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to