From: Greg KH <gregkh@linuxfoundation.org>
To: Konstantin Ryabitsev <mricon@kernel.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: Sun, 3 Feb 2013 18:48:00 -0600 [thread overview]
Message-ID: <20130204004800.GC6243@kroah.com> (raw)
In-Reply-To: <510AAF4F.6060201@kernel.org>
On Thu, Jan 31, 2013 at 12:52:15PM -0500, Konstantin Ryabitsev wrote:
> 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.
That would mean I can't do kernel releases while on ferry rides, which
is probably a good thing in the end :)
> 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.
What causes you to upgrade the version of git on the server? Are you
relying on packages for a distro, or is this "hand installed" by
yourself? As long as I stay in lock-step with your updates, all should
be fine.
Oh, maybe we can report back to the user, the version of git that is
being used on the server, if the checksums don't match, so that I know
to at least see if my version is different from yours?
thanks,
greg k-h
next prev parent reply other threads:[~2013-02-04 3:23 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
2013-02-04 0:48 ` Greg KH [this message]
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=20130204004800.GC6243@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=mricon@kernel.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).