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

Reply via email to