Re: changeset included in a particular tag

[Mike Miller]

Hi Glenn, I'm moving this to the maintainers list, this is the best
place to discuss development or ask questions about the Octave mercurial
repository (and bring the answers to the attention of other developers).

On Mon, Feb 03, 2014 at 22:18:40 +0000, Glenn Golden wrote:
> A question though: This is not specific to this bug but I'll ask it here
> anyway: Not being familiar with Mercurial, I'm wondering what is the "correct"
> way to determine whether a given commit is present within a specific numbered
> version of Octave (as reported by version())?  I looked at the "log" view of
> the commit list
> 
>    http://hg.savannah.gnu.org/hgweb/octave/log
> 
> but the only thing I see giving a hint about the points in time at which
> numbered releases were made is entries with descriptive text like "snapshot
> x.y.z". Such entries can of course be located via search within the list using
> that "snapshot" keyword, and then the date compared to the date of the commit
> you're interesting in knowing about. But I'm wondering if there's a more
> streamlined way to accomplish this?

I've found the following two mercurial patterns useful.

1.

  hg log -r "tag() and d99785217634::" --template "{tags}\n"

This one lists all tags in the working repository that have been made
since the specified changeset. This is roughly like the git command
"git tag --contains".

2.

  hg log -r "d99785217634 and ::tag(\"release-3-8-0\")"

This lists the given changeset if and only if it is a proper ancestor of
the specified tag "release-3-8-0" (in this case it is). If I substitute
a newer changeset, e.g. the tip of the default branch right now,

  hg log -r "cb377af34c00 and ::tag(\"release-3-8-0\")"

then I get no output, meaning it is not present in the history of the
specified tag.

See "hg help revsets" for more ways to extract subsets of the history.

Others (esp. Jordi) may have other mercurial wisdom.

HTH,

-- 
mike