Joan Picanyol i Puig schrieb:
(...)
Hello Joan,
first you have to understand, that tags in Fossil are what other VCSs
call properties.
That means, there is the possibility to assign a value to a property/tag
if one wants to.
Then those properties/tags can be chosen to propagate automatically down
the descendants chain of child revisions, or they are only valid for a
certain commit only.
>> How is "tag cancel" supposed to work and how am I supposed verify it?
If you chose to cance a tag/property it means, that the tag will not be
regarded as associated with that commit anymore. It is still sitting on
this commit, but will not apply on it. If the tag had a value, that
value is lost afterwards. Furthermore the tag will not any longer
propagate to the descendants if it was a propagating tag. Therefore it
is also cancelled for the descendants.
You can verify this via the 'fossil ui' command, that show you those
tags striked out.
(...)
> ** If tagtype is 2 then the tag is being propagated from an
> ** ancestor node. If tagtype is 0 it means a propagating tag is
> ** being blocked.
>
>> Where are the "magic" tags modified by "--raw" defined?
>
> See above. Looking at the source it seems that "--raw" merely disables
> de automatic handling of the "sym-" prefix for the tagname.
Yes! If you create a tag via option "--propagate" the tag type is
propagating. If you issue a "fossil tag cancel ..." the tag type will be
propagation blocked (or tag cancelled) AFAIR ...
> I'm confused on the existance of branch=branchname vs. sym-branchname.
> It appears redundant to me...
All tags that begin with prefix "sym-" can be used at command line
instead of the SHA1 sum of a commit. So at your example above I could
use "fossil co branchname" because the tag was called "sym-branchname".
The last commit with that tag applied will be checked out then.
The property "branch" does not contain any "sym-" prefix and therefore
*cannot* being used at command line to select a commit instead of using
its SHA1 sum.
But as it has assigned a value to it ("branch=branchname") Fossil know
on which branch the current commit currently resides. If there were no
such property, Fossil wouldn't know the current branch, as there could
be more than one tag with a "sym-" prefix prepended -- propagating or
not (e.g. release, fix, testing, ...)
Best regards and happy Fossiling,
chi :-)
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
