On 8/3/2015 3:24 PM, Warren Young wrote: >> After making this mistake, I know I'm supposed to move the bad commit to >> a hidden branch > > Who supposes this, and why do you take their opinion as normative?
When a commit to Fossil causes a problem, I've seen drh move it to a branch (usually not hidden though since he's moving someone else's work) rather than merely following it up with a commit that backs it out. One technical reason for this is to facilitate bisect by striving for every commit on a stable branch compile and run. > I thought I saw reference on this list to a way to lop off the > most-recent checkin on a particular branch, but I couldn’t figure out > how the last time I tried. Is this the mechanism? Using the web interface, you can edit the existing check-in to be in a branch (I usually use the name "mistake" if it's going to be hidden and superseded) that is closed and hidden. -- Andy Goth | <andrew.m.goth/at/gmail/dot/com>
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
