From: Ken Moffat <zarniwhoop@ntlworld.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Vicent Martí" <tanoku@gmail.com>,
"Stefan Näwe" <stefan.naewe@atlas-elektronik.com>,
"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 20:30:30 +0000 [thread overview]
Message-ID: <20140122203030.GB14211@milliways> (raw)
In-Reply-To: <xmqqlhy7yjjp.fsf@gitster.dls.corp.google.com>
On Wed, Jan 22, 2014 at 10:10:18AM -0800, Junio C Hamano wrote:
> Vicent Martí <tanoku@gmail.com> writes:
>
> >> Do these consume CPU every time somebody asks for a tarball? That
> >> might be considered "wrong" depending on the view.
> >
> > No, our infrastructure caches frequently requested tarballs so they
> > don't have to be regenerated on the fly.
>
> Thanks. That is certainly good enough for consumers, and better
> than having to manually create and upload for me ;-)
Two questions: Does regenerating (e.g. if the tarball has dropped
out of the cache) change its sums (md5sum or similar) ? In (beyond)
linuxfromscratch we use md5sums to verify that a tarball has not
changed. Also, will there be links for manpages and htmldocs
tarballs ?
I note that all of these *are* still available at googlecode for
the moment : https://code.google.com/p/git-core/downloads/list
ĸen
--
das eine Mal als Tragödie, dieses Mal als Farce
next prev parent reply other threads:[~2014-01-22 20:30 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
2014-01-22 17:26 ` Vicent Martí
2014-01-22 18:10 ` Junio C Hamano
2014-01-22 20:30 ` Ken Moffat [this message]
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=20140122203030.GB14211@milliways \
--to=zarniwhoop@ntlworld.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=javierdo1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stefan.naewe@atlas-elektronik.com \
--cc=tanoku@gmail.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.