Hi all: In message <C7F6D0C7DBB14445BAF6F56CB651D6A8@Yulichka>, "Tony Papadimitriou" writes: >I've had the same wish for a long long time. I would like the FOSSIL BRANCH >list to show except for the branch name some kind of description. >Like you mentioned, making the branch name itself long enough would be one >way to tackle this but it is counter-productive as you would need to type >the whole thing each time you need to access that branch. > >So, I think the simplest way to add this functionality *without* causing >backward compatibilities or file format changes is to display the first >commit comment for that particular branch as a description in the BRANCH >list command. > >Although it may not always be the most accurate description for branches >already created, I think in most cases the first branch commit comment >represents a pretty good description about what the branch is about, or why >it had to be created.
Since tags are really just properties, what about a convention for adding a branch-description property along sinde the branch=BRANCHNAME property. Thus to add a description, you can run: fossil add tag branch-description CHECKIN "This branch implements the flooze feature, see the BRANCH:flooble wiki page for details." where checkin is the revision with the branch= property set. As an enhancement to the branch command fossil branch new BRANCH-NAME BASIS ?OPTIONS? add an option "--description" that sets the value for the branch-description value at branch time. According to http://www.fossil-scm.org/index.html/doc/trunk/www/branching.wiki this should work to associate metadata with a checkin artifact. Comments? -- -- rouilj John Rouillard =========================================================================== My employers don't acknowledge my existence much less my opinions. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
