On Fri, May 15, 2015 at 2:21 PM, Richard Hipp <d...@sqlite.org> wrote: > On 5/15/15, Lluís Batlle i Rossell <vi...@viric.name> wrote: >> >> I also dislike that branches are not part of the stored history, and >> nothing can be checked about old branches (integrated, destroyed, etc). >> > > Huh. I didn't realize that. You mean that there is nothing > equivalent to https://www.fossil-scm.org/fossil/brlist in Git? GitHub > seems to give me some nothing of a list of branches (though clearly > not as useful as the page linked above). Maybe this is only branches > that still have a HEAD - that have not been merged and closed? > > Can you talk more about this problem, from the point of view of > someone whose Git experience is limited?
In fossil a tag is a piece of information (name, plus optional value) attached to a revision. The same information can be attached to many revisions. A branch is a tag flagged to be automatically propagated to child revisions when they are committed. That means that all revisions of a branch have the branch name associated with them. In git a tag is a named pointer to a revision, stored outside of history, separate from revisions. A branch is simply a tag whose pointer gets moved to a child revision when it is committed. A tag or branch label can only be associated with a _single_ revision, AFAIK. -- % Tcl'2015 Oct 19-23 = http://www.tcl.tk/community/tcl2015/cfp.html % EuroTcl'15 June 20-21 = http://www.eurotcl.tcl3d.org/ Andreas Kupries Senior Tcl Developer Code to Cloud: Smarter, Safer, Faster™ F: 778.786.1133 andre...@activestate.com, http://www.activestate.com Learn about Stackato for Private PaaS: http://www.activestate.com/stackato _______________________________________________ fossil-dev mailing list fossil-dev@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/fossil-dev
