Re: [fossil-users] Convenient command for standardizing and simplifying marking a commit as a mistake.
On Mar 20, 2015 5:05 AM, Henry Adisumarto henry.adisuma...@gmail.com wrote: Hi, I wonder why there isn’t a command for simplifying the process of marking a commit as a mistake. So with a single command, fossil will: ·Move the commit and its derived commits to mistake branch. What about repos which use non-English branch names? ·If there is a leaf in the branch, the leaf will be closed. ·The mistaken commits will be hidden from the timeline. i have always disliked the hiding feature. ·If any of the mistaken commits have been merged into another branch, the mistaken commits will be backed out from the valid branches. That implies automatically committing after backing out, which makes some people nervous, as it amounts to checking in untested changes. There are failure cases here, e.g. when multiple branches merge into the line which this op would want to back something out of. - stephan (Sent from a mobile device, possibly from bed. Please excuse brevity, typos, and top-posting.) ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Convenient command for standardizing and simplifying marking a commit as a mistake.
2015-03-20 13:41 GMT+01:00 Stephan Beal sgb...@googlemail.com: I wonder why there isn’t a command for simplifying the process of marking a commit as a mistake. So with a single command, fossil will: ·The mistaken commits will be hidden from the timeline. i have always disliked the hiding feature. I like the hiding feature ... ;-) ... but it should be used sparingly just as shunning. It shouldn't be made too easy, otherwise people will be more sloppy because any mistake can be corrected easily anyway. ·If any of the mistaken commits have been merged into another branch, the mistaken commits will be backed out from the valid branches. That implies automatically committing after backing out, which makes some people nervous, as it amounts to checking in untested changes. There are failure cases here, e.g. when multiple branches merge into the line which this op would want to back something out of. Agreed. I don't think any simplification would be a good idea. Sorry! Regards, Jan Nijtmans ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
