On Mon, Jul 17, 2017 at 6:33 AM, Damien Sykes-Lindley < dam...@dcpendleton.plus.com> wrote:
> Hi there, > Is there a way of removing or preventing the creation of the “initial > empty checkin”? I personally can’t see any practical uses for that, unless > the implementation somehow requires it. > Historically, the implementation needed it to "seed" the db with starting point for db record IDs. At one point there was an option to create a new repo without that (as opposed to removing a commit - that has never been implemented), but that feature seems to have been removed in the meantime (i don't recall if that feature was ever in the trunk, but i know it was implemented about 3 or 4 years ago). Completely removing a commit can't be done in fossil except, _hypothetically_, by removing every commit, starting at the newest one, which leads to that commit (think of it as a stack of commits, where one could "pop off" each commit in that stack). That's hypothetically possible, but it's never been implemented. Also, this checkin seems to be automatically sent to trunk. Is there any > way of renaming this branch, either on the creation of the repository or > later on? > Yes: fossil ui visit the timeline visit the checkin see the "Other Links" line and click on the "edit" link see the "Branching" line: change the name of the branch to whatever you like, then click the Apply Changes button. -- ----- 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 fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
