Fossil: View Ticket

Ticket UUID:	d1cdb1bfa181487f2c5944f94e3b63f26e440be0
Title:	Leaf functionality unclear
Status:	Deferred	Type:	Documentation
Severity:	Minor	Priority:
Subsystem:		Resolution:	Not_A_Bug
Last Modified:	2009-01-29 16:43:42
Version Found In:
Description & Comments:
This is a request for documentation that covers leaves. I assume it is similar or synonymous with branching in other SCMs, but I wasn't able to find any documentation that goes into detail about it or confirms it. If the documentation already exists, I apologize, in which case, perhaps it can just be made easier to stumble upon. kkinnell added on 2008-11-19 15:25:47: There is quite a bit of fossil that is not yet verbosely documented, or documented at all. The project hasn't had anyone who's primarily a documenter until recently (a lot of projects suffer from this problem.) This explanation of distributed SCM, while it fails to mention fossil (a glaring oversight!) will at least be another source for clarifying things a bit. kkinnell added on 2008-11-19 16:42:18: Sorry, I'm trying to do too much at once and doing it all badly... I meant to mention that the explanation doesn't explicitly say anything about what a "leaf" is, but it gives a good overview that should make what a leaf is clearer. A leaf is a good old computer science bottom-of-the-tree node. It's derived from a basis, and has no descendants. Branches and leaves in a distributed scm are just side effects a lot of the time; it's up to the participants to merge them back into a basis. eric added on 2008-11-19 16:56:23: At one point it mentions "heads" - it means leaves.