From: Konstantin Ryabitsev <mricon@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Junio C Hamano <gitster@pobox.com>,
Rene Scharfe <rene.scharfe@lsrfire.ath.cx>,
git@vger.kernel.org
Subject: Re: "git archve --format=tar" output changed from 1.8.1 to 1.8.2.1
Date: Thu, 31 Jan 2013 12:52:15 -0500 [thread overview]
Message-ID: <510AAF4F.6060201@kernel.org> (raw)
In-Reply-To: <20130131174103.GA20111@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 850 bytes --]
On 31/01/13 12:41 PM, Greg KH wrote:
> Ugh, uploading a 431Mb file, over a flaky wireless connection (I end up
> doing lots of kernel releases while traveling), would be a horrible
> change. I'd rather just keep using the same older version of git that
> kernel.org is running instead.
Well, we do accept compressed archives, so you would be uploading about
80MB instead of 431MB, but that would still be a problem for anyone
releasing large tarballs over unreliable connections. I know you
routinely do 2-3 releases at once, so that would still mean uploading
120-180MB.
I don't have immediate statistics on how many people release using "kup
--tar", but I know that at least you and Linus rely on that exclusively.
Regards,
--
Konstantin Ryabitsev
Systems Administrator
Linux Foundation, kernel.org
Montréal, Québec
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 730 bytes --]
next prev parent reply other threads:[~2013-01-31 17:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-31 17:28 "git archve --format=tar" output changed from 1.8.1 to 1.8.2.1 Greg KH
2013-01-31 17:32 ` Junio C Hamano
2013-01-31 17:41 ` Greg KH
2013-01-31 17:52 ` Konstantin Ryabitsev [this message]
2013-02-04 0:48 ` Greg KH
2013-01-31 18:16 ` Junio C Hamano
2013-02-04 0:45 ` Greg KH
2013-02-04 5:05 ` Junio C Hamano
2013-02-04 18:26 ` Greg KH
2013-01-31 18:33 ` René Scharfe
2013-02-04 0:42 ` Greg KH
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=510AAF4F.6060201@kernel.org \
--to=mricon@kernel.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=gregkh@linuxfoundation.org \
--cc=rene.scharfe@lsrfire.ath.cx \
/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).