Re: [fossil-users] What is a baseline?

2014-07-18 Thread Stephan Beal
On Fri, Jul 18, 2014 at 8:30 PM, Warren Young war...@etr-usa.com wrote:

 fossil help timeline talks about a BASELINE.  I've discovered by playing
 that it can be an artifact ID, but I assume there has to be more to it than
 that, else why use a different term?

 Neither the Schimpf book nor fossil help really explain the term.  It
 doesn't appear on the documentation index page or in the FAQ.


A baseline is a side-effect of fossil's delta manifests. Originally,
fossil required that all files belonging to a give version be included in
that checkin's manifest (the official metadata). That proved to be
problematic for repos with large numbers (thousands) of files, as it has to
record thousands of files in a list when only one changed. List member
Joerg Sonnenberg (spelling?) urged Richard to find a solution, and that
solution was delta manifests. A baseline is a normal checkin record. A
delta manifest is a checkin record which records only files which changed
between its own version and the baseline version. Any given non-delta
checkin can be a baseline for arbitrary other delta manifests. If a delta
gets too big, a new baseline checkin is created with all the files listed
in it, and further deltas can be generated from that one.

i've got a simple browser which might make this clearer:

http://fossil.wanderinghorse.net/repos/libfossil/cgidemo/index.cgi/manifest

see the Parent/Baseline links, click those, and note the UUIDs. Sometimes
the parent and baseline are the same, but not always. Typically any given
baseline stays a baseline of its successors until the list of file changes
gets to some computed portion of the original file list, at which point it
is considered to be too far removed from the current version and a new
baseline is created.

So, in short: a baseline manifest is simply a checkin record (i.e.
manifest) which is _not_ a delta manifest. Whether or not it actually
acts as a baseline for any deltas is unimportant (maybe it does not now,
but will tomorrow).



 Can a tag name be a baseline?


No - only checkin records can. Originally, checkins were called manifests,
but the word manifest now has several meanings. See:

http://fossil.wanderinghorse.net/repos/libfossil/doxygen/page_terminology.html

i hope that makes some sort of sense.

-- 
- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
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


Re: [fossil-users] What is a baseline?

2014-07-18 Thread Richard Hipp
Baseline is an older name for check-in.  It drives from DO-178B
language.

We should updates the timeline help to say check-in instead, as that will
be clearer to most readers, I think.


On Fri, Jul 18, 2014 at 2:30 PM, Warren Young war...@etr-usa.com wrote:

 fossil help timeline talks about a BASELINE.  I've discovered by playing
 that it can be an artifact ID, but I assume there has to be more to it than
 that, else why use a different term?

 Neither the Schimpf book nor fossil help really explain the term.  It
 doesn't appear on the documentation index page or in the FAQ.

 Can a tag name be a baseline?
 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users




-- 
D. Richard Hipp
d...@sqlite.org
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


Re: [fossil-users] What is a baseline?

2014-07-18 Thread Richard Hipp
On Fri, Jul 18, 2014 at 2:40 PM, Stephan Beal sgb...@googlemail.com wrote:

 On Fri, Jul 18, 2014 at 8:30 PM, Warren Young war...@etr-usa.com wrote:

 fossil help timeline talks about a BASELINE.  I've discovered by
 playing that it can be an artifact ID, but I assume there has to be more to
 it than that, else why use a different term?

 Neither the Schimpf book nor fossil help really explain the term.  It
 doesn't appear on the documentation index page or in the FAQ.


 A baseline is a side-effect of fossil's delta manifests.


That's a newer and unrelated meaning of the word baseline, that is still
meaningful.  I think the word baseline in the timeline help comment is
the older, obsolete alias for check-in.


 Originally, fossil required that all files belonging to a give version be
 included in that checkin's manifest (the official metadata). That proved
 to be problematic for repos with large numbers (thousands) of files, as it
 has to record thousands of files in a list when only one changed. List
 member Joerg Sonnenberg (spelling?) urged Richard to find a solution, and
 that solution was delta manifests. A baseline is a normal checkin
 record. A delta manifest is a checkin record which records only files which
 changed between its own version and the baseline version. Any given
 non-delta checkin can be a baseline for arbitrary other delta manifests. If
 a delta gets too big, a new baseline checkin is created with all the
 files listed in it, and further deltas can be generated from that one.

 i've got a simple browser which might make this clearer:

 http://fossil.wanderinghorse.net/repos/libfossil/cgidemo/index.cgi/manifest

 see the Parent/Baseline links, click those, and note the UUIDs. Sometimes
 the parent and baseline are the same, but not always. Typically any given
 baseline stays a baseline of its successors until the list of file changes
 gets to some computed portion of the original file list, at which point it
 is considered to be too far removed from the current version and a new
 baseline is created.

 So, in short: a baseline manifest is simply a checkin record (i.e.
 manifest) which is _not_ a delta manifest. Whether or not it actually
 acts as a baseline for any deltas is unimportant (maybe it does not now,
 but will tomorrow).



 Can a tag name be a baseline?


 No - only checkin records can. Originally, checkins were called manifests,
 but the word manifest now has several meanings. See:


 http://fossil.wanderinghorse.net/repos/libfossil/doxygen/page_terminology.html

 i hope that makes some sort of sense.

 --
 - stephan beal
 http://wanderinghorse.net/home/stephan/
 http://gplus.to/sgbeal
 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




-- 
D. Richard Hipp
d...@sqlite.org
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


Re: [fossil-users] What is a baseline?

2014-07-18 Thread Stephan Beal
On Fri, Jul 18, 2014 at 8:40 PM, Stephan Beal sgb...@googlemail.com wrote:

 i've got a simple browser which might make this clearer:

 http://fossil.wanderinghorse.net/repos/libfossil/cgidemo/index.cgi/manifest


This one's a good example:

http://fossil.wanderinghorse.net/repos/libfossil/cgidemo/index.cgi/manifest/98be7a7c10f23ccae709766

the Baseline is actually several versions back from the parent. If you
first follow the Baseline link, then go Back and follow the Parent link (a
few times), you should see that the next several Baseline links show up as
visited, as those versions all share the same baseline manifest.

-- 
- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
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


Re: [fossil-users] What is a baseline?

2014-07-18 Thread Warren Young

On 7/18/2014 12:39, Richard Hipp wrote:


We should updates the timeline help to say check-in instead, as that
will be clearer to most readers, I think.


Sounds good.  Baseline appears in the help for

/ci_edit
/doc
/info
/zip
3-way-merge
ci  (as --baseline)
descendants
merge
revert
stash
tag
timeline

The help for fossil tag talks about a hexadecimal baseline or 
artifact ID.  Is there a difference?



Can a tag name be a baseline?


My understanding is that a non-propagating tag is an alias for an 
artifact ID, and can be used in the same places.  True?

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


Re: [fossil-users] What is a baseline?

2014-07-18 Thread Richard Hipp
On Fri, Jul 18, 2014 at 2:55 PM, Warren Young war...@etr-usa.com wrote:

 On 7/18/2014 12:39, Richard Hipp wrote:


 We should updates the timeline help to say check-in instead, as that
 will be clearer to most readers, I think.


 Sounds good.  Baseline appears in the help for

 /ci_edit
 /doc
 /info
 /zip
 3-way-merge
 ci  (as --baseline)
 descendants
 merge
 revert
 stash
 tag
 timeline

 The help for fossil tag talks about a hexadecimal baseline or artifact
 ID.  Is there a difference?


Maybe.  A check-in is a particular kind of artifact that defines a
collection of files that is being checked in as a complete version of the
program.  An artifact ID can refer to thinks other than check-ins, for
example specific versions of files or tickets or wiki pages, etc.

In other words, a check-in is always an artifact but an artifact is not
always a check-in.




  Can a tag name be a baseline?


 My understanding is that a non-propagating tag is an alias for an artifact
 ID, and can be used in the same places.  True?


Any tag can be used as a check-in name.  It doesn't have to be
non-propagating and it doesn't have to be unique.  In the event that two or
more check-ins both carry the same tag (perhaps because the tag propagates)
then the one with the most recent timestamp is selected.




 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users




-- 
D. Richard Hipp
d...@sqlite.org
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


Re: [fossil-users] What is a baseline?

2014-07-18 Thread Ron W
On Fri, Jul 18, 2014 at 2:55 PM, Warren Young war...@etr-usa.com wrote:

 Baseline appears in the help for

 ci  (as --baseline)


If I understand the description in the help, --baseline forces the created
manifest to be a baseline manifest..

This seems reasonable. Perhaps the description can be made clearer? Also,
add a description (somewhere) of baseline vs delta manifest.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


Re: [fossil-users] What is a baseline?

2014-07-18 Thread Richard Hipp
On Fri, Jul 18, 2014 at 3:23 PM, Ron W ronw.m...@gmail.com wrote:

 On Fri, Jul 18, 2014 at 2:55 PM, Warren Young war...@etr-usa.com wrote:

 Baseline appears in the help for

 ci  (as --baseline)


 If I understand the description in the help, --baseline forces the created
 manifest to be a baseline manifest..

 This seems reasonable. Perhaps the description can be made clearer? Also,
 add a description (somewhere) of baseline vs delta manifest.


That use of the word baseline is in accordance with the meaning described
by Stephan, not the older obsolete alias for check-in that is written as
BASELINE on the timeline help page.

Yes, that is confusing.  And yes, it needs to be fixed.





 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users




-- 
D. Richard Hipp
d...@sqlite.org
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users