git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Dan Johnson <computerdruid@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
	Graham Ballantyne <grahamb@sfu.ca>,
	git@vger.kernel.org
Subject: Re: Incorrect v1.7.10.4 tag on github?
Date: Mon, 2 Jul 2012 16:08:15 -0400	[thread overview]
Message-ID: <20120702200815.GA3179@sigill.intra.peff.net> (raw)
In-Reply-To: <CAPBPrnspD3uC6_wd7nqMUVgHSt4Frwy8UaYL6fU73kJKX6=XWQ@mail.gmail.com>

On Mon, Jul 02, 2012 at 03:52:31PM -0400, Dan Johnson wrote:

> > 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).
> 
> I just noticed that the download buttons (for tarballs) on gitscm.com
> all point to the github tag list ( https://github.com/git/git/tags )
> instead of the location pointed to by your [ANNOUNCE] message (
> http://code.google.com/p/git-core/downloads/list )

Ick. Yeah, I would think it would definitely want to point to Junio's
built tarballs, because they contain the built 'configure' script.
Otherwise, the downloader would need to have autoconf installed if they
wanted to use configure.

> If you do something special as part of releasing these tarballs, is
> this something that should be corrected? I can look at the source and
> do a pull request for gitscm.com a little later, if needed.

I suspect that the tarballs link on git-scm.com should at the very least
point to:

  http://code.google.com/p/git-core/downloads/list

That list is a little overwhelming because it contains the html and
manpage tarballs, too. It might make sense to provide a cut-down list
(e.g., only source tarballs, and only the latest for each minor version,
and omit -rc candidates for already-released versions). But that would
be a lot more involved.

-Peff

  reply	other threads:[~2012-07-02 20:08 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
2012-07-02 19:52     ` Dan Johnson
2012-07-02 20:08       ` Jeff King [this message]
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=20120702200815.GA3179@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=computerdruid@gmail.com \
    --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).