From: Junio C Hamano <gitster@pobox.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Rene Scharfe <rene.scharfe@lsrfire.ath.cx>,
git@vger.kernel.org, Konstantin Ryabitsev <mricon@kernel.org>
Subject: Re: "git archve --format=tar" output changed from 1.8.1 to 1.8.2.1
Date: Thu, 31 Jan 2013 10:16:27 -0800 [thread overview]
Message-ID: <7vr4l1gqv8.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20130131174103.GA20111@kroah.com> (Greg KH's message of "Thu, 31 Jan 2013 18:41:03 +0100")
Greg KH <gregkh@linuxfoundation.org> writes:
> On Thu, Jan 31, 2013 at 09:32:12AM -0800, Junio C Hamano wrote:
>
>> How about fixing kup to teach the "let's cheat and let the other end
>> run 'git archive', if the resulting archive and GPG signature
>> locally created does match, we do not have to transfer the tarball
>> itself" trick a fall-back mode that says "but if the signature does
>> not match, then transfer the bulk used to create the signature to
>> the remote anyway". This fallback can and should of course be
>> useful for the compressed patch transfer.
>
> 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.
Then how about fixing kup to try both versions of Git? There will
be people who run different versions of Git anyway, and kup should
not be preventing Git from helping people on other platforms, or
improving its output in general.
next prev parent reply other threads:[~2013-01-31 18:16 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
2013-01-31 18:16 ` Junio C Hamano [this message]
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=7vr4l1gqv8.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--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).