git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Graham Ballantyne <grahamb@sfu.ca>, git@vger.kernel.org
Subject: Re: Incorrect v1.7.10.4 tag on github?
Date: Fri, 15 Jun 2012 15:17:23 -0400	[thread overview]
Message-ID: <20120615191723.GA26651@sigill.intra.peff.net> (raw)
In-Reply-To: <7vvcis9ylx.fsf@alter.siamese.dyndns.org>

On Fri, Jun 15, 2012 at 12:14:18PM -0700, Junio C Hamano wrote:

> > It builds with the right version from the git repository (which runs
> > git-describe and sees we are on the v1.7.10.4 tag), but exporting the
> > tag's contents and building fails. I suspect that the git-1.7.10.4
> > tarball on kernel.org would also have the same problem.
> 
> It builds correctly if you download the tarball from the official
> location in the [ANNOUNCE] message.  This is because the build
> procedure for the official tarball does a bit more than just running
> "git archive-tar", which is what gitweb download interface does
> (namely, it adds the correct "version" file).

Thanks. I should have checked before responding. If it is just the
output of "git archive", and the problem is restricted to one version,
then I am not too worried about it. Re-tagging is out of the question,
anyway.

-Peff

  reply	other threads:[~2012-06-15 19:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-15 16:51 Incorrect v1.7.10.4 tag on github? Graham Ballantyne
2012-06-15 18:25 ` Jeff King
2012-06-15 19:14   ` Junio C Hamano
2012-06-15 19:17     ` Jeff King [this message]
2012-07-02 19:52     ` Dan Johnson
2012-07-02 20:08       ` Jeff King
2012-07-02 21:00       ` Junio C Hamano
2012-07-02 21:11         ` Scott Chacon
2012-07-02 21:58           ` Junio C Hamano

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=20120615191723.GA26651@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=grahamb@sfu.ca \
    /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).