Re: Sources for 3.18-rc1 not uploaded
- From
Konstantin Ryabitsev <konstantin@linuxfoundation.org>
- Date
- Oct 20, 2014, 18:37 UTC
- Message-ID
- <54455655.9010406@linuxfoundation.org>
- In-Reply-To
- <xmqqoat6389s.fsf@gitster.dls.corp.google.com>
On 20/10/14 02:28 PM, Junio C Hamano wrote:
Show 7 quoted lines
> 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