On Wed, Aug 16, 2017 at 7:59 PM, Steve Schow <[email protected]> wrote: > Is that possible at all or if not, what is the best way to handle that kind of situation with fossil?
Fossil is designed to never forget anything, not even mistakes. It's possible to move a commit to a new branch, thereby "kind of hiding it", but not to remove it. To move a commit: fossil ui select the commit in the timeline Find the "edit" link and click it. Find the "Make this check-in the start of a new branch named", give it a name, and check that checkbox. Fossil has an option called "shunning" for removing "really bad" mistakes, such as credentials and illegally copied materials, but that is a "nuclear option" which can have side effects and is not intended to be used for "honest, but harmless, mistakes". -- ----- stephan beal http://wanderinghorse.net/home/stephan/ "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
