On Sun, 6 Nov 2011 16:22:36 +0400, Konstantin Khomoutov <flatw...@users.sourceforge.net> wrote: >I think the meaning of these hashes is reversed: artifact is a particular >version of a particular file according to [1], > so the first hash here identifies the commit the artifact identified by the > second hash is a part of. >You can verify this simply by correlating the output of `fossil finfo` >with the output of `fossil timeline`.
Thanks for the info. Apparently, when running "fossil finfo myfile", the first hash identifies the whole commit (ie. all the files whose changes were commited when running "fossil commit") while the second hash identifies the particular commit for that particular file: C:\Projects\Project1>fossil finfo Form1.vb 2011-11-05 [6a07f19e02] Code complete (user: Joe, artifact: [9735460a2c]) C:\Projects\Project1>fossil artifact 6a07f19e02 => List all the files affected by that commit C:\Projects\Project1>fossil artifact 9735460a2c => List the state of the file when it was commited One thing I'm not clear about, is how "fossil timeline" works: When using "-n 5", it shows three lines, while "-n 10" shows five lines, and "-n 20" shows eleven :-/ http://fossil-scm.org/index.html/help?cmd=timeline What does "timeline" show, really? _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
