git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Miklos Vajna <vmiklos@frugalware.org>
Cc: "Shawn O. Pearce" <spearce@spearce.org>, git@vger.kernel.org
Subject: Re: git describe weird behaviour
Date: Wed, 8 Dec 2010 22:28:02 -0500	[thread overview]
Message-ID: <20101209032802.GA18773@sigill.intra.peff.net> (raw)
In-Reply-To: <20101209013323.GJ22105@genesis.frugalware.org>

On Thu, Dec 09, 2010 at 02:33:23AM +0100, Miklos Vajna wrote:

> On Wed, Nov 10, 2010 at 03:03:34PM +0100, Miklos Vajna <vmiklos@frugalware.org> wrote:
> > > The patch below implements that in a very rough-and-dirty way. It does
> > > find the 1.4 tag in your repository that you expect. However:
> > 
> > Yes, works here as well:
> > 
> > $ ~/git/git/git describe
> > 1.4pre1-210-g48b67cd
> 
> Any update on this? I still have this patch in my tree to get correct
> git describe output. :)

Sorry, no, I haven't had time to think about it, and I probably won't
for a few more weeks at least.

The patch I posted was giving some really weird results for git.git,
though, so it is definitely not OK for inclusion as-is.

-Peff

  reply	other threads:[~2010-12-09  3:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-10  1:00 git describe weird behaviour Miklos Vajna
2010-11-10  4:14 ` Jeff King
2010-11-10  8:47   ` Maaartin
2010-11-10  8:52   ` Thomas Rast
2010-11-10 14:03   ` Miklos Vajna
2010-12-09  1:33     ` Miklos Vajna
2010-12-09  3:28       ` Jeff King [this message]
2010-11-10 19:38 ` Junio C Hamano
2010-11-10 20:40   ` Miklos Vajna
2010-11-10 21:24     ` Jonathan Nieder
2010-11-10 22:07       ` Miklos Vajna

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=20101209032802.GA18773@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=spearce@spearce.org \
    --cc=vmiklos@frugalware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).