All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <ukleinek@strlen.de>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
	Pierre Habouzit <madcoder@debian.org>,
	Erez Zilber <erezzi.list@gmail.com>
Subject: Re: [RFC PATCH] describe: Make --tags and --all match lightweight tags more often
Date: Sun, 12 Oct 2008 20:29:13 +0200	[thread overview]
Message-ID: <20081012182913.GA8858@strlen.de> (raw)
In-Reply-To: <20081010165952.GI8203@spearce.org>

On Fri, Oct 10, 2008 at 09:59:52AM -0700, Shawn O. Pearce wrote:
> If the caller supplies --tags they want the lightweight, unannotated
> tags to be searched for a match.  If a lightweight tag is closer
> in the history, it should be matched, even if an annotated tag is
> reachable further back in the commit chain.
> 
> The same applies with --all when matching any other type of ref.
> 
> Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
> ---
> 
>  This come out of the discussions earlier last week, where folks
>  were confused about the meaning of --tags and wanted to see it
>  behave as they expected, which was to match the nearest tag,
>  no matter its "type".
> 
>  The code is unchanged from what I sent out before, but now it has
>  updated test vectors and a commit message.
> 
>  Thoughts?
As I already told earlier, this is exactly how I would expect it.

>  static int debug;	/* Display lots of verbose info */
> -static int all;	/* Default to annotated tags only */
> -static int tags;	/* But allow any tags if --tags is specified */
> +static int all;	/* Any valid ref can be used */
> +static int tags;	/* Either lightweight or annotated tags */
Maybe the last comment should better read:

	/* allow lightweight tags */

?  Apart from this one nitpick:

Acked-By: Uwe Kleine-König <ukleinek@strlen.de>

Thanks
Uwe

  parent reply	other threads:[~2008-10-12 18:30 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-28 13:48 git-describe doesn't show the most recent tag Erez Zilber
2008-09-28 13:55 ` Pierre Habouzit
2008-09-28 14:29   ` Erez Zilber
2008-09-28 14:39     ` Pierre Habouzit
2008-09-28 15:03       ` Pierre Habouzit
2008-09-28 15:12         ` [PATCH] doc: enhance git describe --tags help Pierre Habouzit
2008-09-29 15:01           ` Shawn O. Pearce
2008-09-30  8:39             ` Pierre Habouzit
2008-10-10 16:59               ` [RFC PATCH] describe: Make --tags and --all match lightweight tags more often Shawn O. Pearce
2008-10-10 17:12                 ` Pierre Habouzit
2008-10-10 18:18                   ` Junio C Hamano
2008-10-13 14:32                     ` Shawn O. Pearce
2008-10-13 14:39                   ` [PATCH v2] " Shawn O. Pearce
2008-10-15 12:54                     ` Santi Béjar
2008-10-11 22:47                 ` [RFC PATCH] " Andreas Ericsson
2008-10-12 18:00                   ` Shawn O. Pearce
2008-10-12 18:13                     ` Andreas Ericsson
2008-10-12 18:29                 ` Uwe Kleine-König [this message]
2008-09-30  9:56             ` [PATCH] doc: enhance git describe --tags help Uwe Kleine-König
2008-09-30 10:09               ` Andreas Ericsson
2008-09-30 19:04               ` Shawn O. Pearce
2008-09-30 22:14                 ` Uwe Kleine-König
2008-09-30 22:26                   ` Shawn O. Pearce
2008-10-15 20:05                     ` Uwe Kleine-König
2008-09-28 15:05       ` git-describe doesn't show the most recent tag Erez Zilber
2008-09-28 14:51     ` Andreas Ericsson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20081012182913.GA8858@strlen.de \
    --to=ukleinek@strlen.de \
    --cc=erezzi.list@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=madcoder@debian.org \
    --cc=spearce@spearce.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.