From: Scott Chacon <schacon@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Dan Johnson <computerdruid@gmail.com>, Jeff King <peff@peff.net>,
Graham Ballantyne <grahamb@sfu.ca>,
git@vger.kernel.org
Subject: Re: Incorrect v1.7.10.4 tag on github?
Date: Mon, 2 Jul 2012 14:11:32 -0700 [thread overview]
Message-ID: <CAP2yMaLy3sBwybMH2LYs9Sg0AigZ-_tAx4SbHOrwr3T6GfLSaw@mail.gmail.com> (raw)
In-Reply-To: <7v7gulzxme.fsf@alter.siamese.dyndns.org>
Hey,
On Mon, Jul 2, 2012 at 2:00 PM, Junio C Hamano <gitster@pobox.com> wrote:
>> 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 )
>
>> If you do something special as part of releasing these tarballs, is
>> this something that should be corrected?
>
> I do not do anything special other than "make dist", but obviously
> anybody's "list of tags" that drive "git archive" won't run it, so
> it is a wrong thing to point at, regardless of who hosts it.
Thanks for letting me know - I didn't realize that the built tarballs
were different from the tagged commit trees. I will update the links.
Scott
next prev parent reply other threads:[~2012-07-02 21:11 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
2012-07-02 21:00 ` Junio C Hamano
2012-07-02 21:11 ` Scott Chacon [this message]
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=CAP2yMaLy3sBwybMH2LYs9Sg0AigZ-_tAx4SbHOrwr3T6GfLSaw@mail.gmail.com \
--to=schacon@gmail.com \
--cc=computerdruid@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=grahamb@sfu.ca \
--cc=peff@peff.net \
/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).