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: Sun, 03 Feb 2013 21:05:55 -0800 [thread overview]
Message-ID: <7vvca8653g.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20130204004512.GB6243@kroah.com> (Greg KH's message of "Sun, 3 Feb 2013 18:45:12 -0600")
Greg KH <gregkh@linuxfoundation.org> writes:
>> 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.
>
> I think the combinations of different versions of git that would have to
> be installed on kernel.org to handle stuff like this as things change
> over time, wouldn't be worth it.
You make it sound as if you have to pick the right one among 47
different versions, but I think over the lifetime of Git there was
only one time that output from "diff" would have affected the kup's
trick to avoid the transmission of patch text, and another that
output from "tar-tree" (aka "archive --format=tar") would have
afffected the transmission of tarballs. I do think it is feasible
if "kup" wanted to.
> The number of people this affects right now is only one (me), given that
> the offending file is not in Linus's tree right now, so he doesn't have
> issues with uploading new releases.
As a tree grows larger over time, it may be just a matter of time
for somebody else to be hit by another deep path, though.
next prev parent reply other threads:[~2013-02-04 5:06 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
2013-02-04 0:45 ` Greg KH
2013-02-04 5:05 ` Junio C Hamano [this message]
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=7vvca8653g.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).