On Thu, Nov 22, 2012 at 9:19 AM, Gilles <[email protected]> wrote:
> Hello
>
> I checked the "help" section and googled for more infos, but am
> still a bit unclear at how to use the "tag" option to add tags to a
> given check-in:
>
> 1. Am I correct in understanding that the "tag" command can be either
> used with "commit"...
>
> "fossil commit -m "Some commit" -tag some tags"
>
> ... or later by calling it with a specific check-in hash?
>
> "fossil tag add ?--raw? ?--propagate? TAGNAME CHECK-IN ?VALUE?"
>
Yes.
>
> 2. How do I find check-in's so that I can assign it one or more tags?
>
Look at the timeline?
>
> 3. I'm not clear about what "--raw" does: "The option --raw allows the
> manipulation of all types of tag sused for various internal purposes
> in fossil. It also shows"cancel" tags for the "find" and "list"
> subcommands."
>
Do not use the --raw option. In fact, I would recommend that you not use
the "tag" command at all if you are not 100% sure what you are doing.
Stick to the --tag option on "fossil commit".
Note that you can include multiple --tag options on a commit. When I
create a new release of SQLite, for example, I'll typically add a couple of
tags and a check-in specific background color, like this:
fossil commit -f --tag release --tag version-3.7.15 --bgcolor "#d0c0ff'
The -f option is to force the commit to go through even though there have
been no changes to the code. Every release gets a "release" tag, so that
we can view all releases on a single page. (See
http://www.sqlite.org/src/timeline?t=release for example.) The
"version-3.7.15" tag is unique to that one check-in.
>
> 4. Are tags the right way to locate a given check-in, through the
> "fossil tag find" command?
>
I guess that depends on which check-in your are looking for.
Most check-ins are untagged (except for the name of the branch they are on,
which is a tag that Fossil adds automatically). I only tag releases or
other important milestones. For other historical check-ins, you can do
"fossil search" to look for them by check-in comment, or "fossil bisect" to
look for them by functionality, or "fossil timeline" to get a list of
check-ins to scan manually. You can also search for specific changes to a
file using the various "annotate" features. It all depends on what kind of
check-in you are searching for.
>
> Thank you.
>
> _______________________________________________
> fossil-users mailing list
> [email protected]
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
--
D. Richard Hipp
[email protected]
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
