From: Junio C Hamano <gitster@pobox.com>
To: "Stefan Näwe" <stefan.naewe@atlas-elektronik.com>
Cc: Javier Domingo Cansino <javierdo1@gmail.com>,
"git\@vger.kernel.org" <git@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [ANNOUNCE] Git v1.9-rc0
Date: Wed, 22 Jan 2014 08:11:33 -0800 [thread overview]
Message-ID: <xmqq7g9syp1m.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <52DFE882.2040605@atlas-elektronik.com> ("Stefan Näwe"'s message of "Wed, 22 Jan 2014 16:49:22 +0100")
Stefan Näwe <stefan.naewe@atlas-elektronik.com> writes:
> Am 22.01.2014 13:53, schrieb Javier Domingo Cansino:
>> Will there be any change on how tarballs are distributed, taking into
>> account that Google will be shutting down Google Code Downloads
>> section[1][2]?
>>
>
> Am I missing something or what's wrong with this:
>
> https://github.com/gitster/git/archive/v1.9-rc0.tar.gz
>
> or any
>
> https://github.com/gitster/git/archive/$TAG.tar.gz
>
> ??
Do these consume CPU every time somebody asks for a tarball? That
might be considered "wrong" depending on the view.
next prev parent reply other threads:[~2014-01-22 16:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-16 21:03 What's cooking in git.git (Jan 2014, #03; Thu, 16) Junio C Hamano
2014-01-21 22:14 ` [ANNOUNCE] Git v1.9-rc0 Junio C Hamano
2014-01-22 12:53 ` Javier Domingo Cansino
2014-01-22 15:42 ` Junio C Hamano
2014-01-22 15:49 ` Stefan Näwe
2014-01-22 16:11 ` Junio C Hamano [this message]
2014-01-22 17:26 ` Vicent Martí
2014-01-22 18:10 ` Junio C Hamano
2014-01-22 20:30 ` Ken Moffat
2014-01-22 21:04 ` Junio C Hamano
2014-01-22 23:11 ` Ken Moffat
2014-01-23 2:09 ` Jeff King
2014-01-23 18:15 ` Junio C Hamano
2014-01-24 23:36 ` Jeff King
2014-01-27 22:56 ` Junio C Hamano
2014-01-28 0:04 ` Jeff King
2014-01-27 17:59 ` Kacper Kornet
2014-01-27 18:58 ` Jonathan Nieder
2014-01-28 12:28 ` Kacper Kornet
2014-01-30 22:20 ` Sitaram Chamarty
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=xmqq7g9syp1m.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=javierdo1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stefan.naewe@atlas-elektronik.com \
/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.