From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Junio C Hamano <gitster@pobox.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: "brian m. carlson" <sandals@crustytoothpaste.net>,
infra-steering@kernel.org, Git Mailing List <git@vger.kernel.org>
Subject: Re: Sources for 3.18-rc1 not uploaded
Date: Mon, 20 Oct 2014 14:37:09 -0400 [thread overview]
Message-ID: <54455655.9010406@linuxfoundation.org> (raw)
In-Reply-To: <xmqqoat6389s.fsf@gitster.dls.corp.google.com>
On 20/10/14 02:28 PM, Junio C Hamano wrote:
> I have to wonder why 10f343ea (archive: honor tar.umask even for pax
> headers, 2014-08-03) is a problem but an earlier change v1.8.1.1~8^2
> (archive-tar: split long paths more carefully, 2013-01-05), which
> also should have broken bit-for-bit compatibility, went unnoticed,
> though. What I am getting at is that correcting past mistakes in
> the output should not be forbidden unconditionally with a complaint
> like this.
I think Greg actually ran into that one, and uses a separate 1.7 git
tree for this reason.
I can update our servers to git 2.1 (which most of them already have),
which should help with previous incompatibilities -- but not the future
ones obviously. :)
-K
next prev parent reply other threads:[~2014-10-20 18:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20141020115943.GA27144@gmail.com>
2014-10-20 15:25 ` Sources for 3.18-rc1 not uploaded Linus Torvalds
2014-10-20 18:28 ` Junio C Hamano
2014-10-20 18:37 ` Konstantin Ryabitsev [this message]
2014-10-20 19:43 ` Junio C Hamano
2014-10-20 21:52 ` Greg KH
2014-10-20 22:28 ` brian m. carlson
2014-10-20 23:17 ` Linus Torvalds
2014-10-21 8:08 ` Michael J Gruber
2014-10-21 16:25 ` Linus Torvalds
2014-10-21 17:25 ` David Kastrup
2014-10-21 18:14 ` Junio C Hamano
2014-10-22 9:42 ` Michael J Gruber
2014-10-23 1:09 ` brian m. carlson
2014-10-26 18:59 ` René Scharfe
2014-10-26 21:15 ` brian m. carlson
2014-10-27 20:19 ` Junio C Hamano
2014-10-20 23:44 ` Konstantin Ryabitsev
2014-10-21 18:59 ` Junio C Hamano
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=54455655.9010406@linuxfoundation.org \
--to=konstantin@linuxfoundation.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=infra-steering@kernel.org \
--cc=sandals@crustytoothpaste.net \
--cc=torvalds@linux-foundation.org \
/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