Re: git archve --format=tar output changed from 1.8.1 to 1.8.2.1

2013-02-04 Thread Greg KH
On Sun, Feb 03, 2013 at 09:05:55PM -0800, Junio C Hamano wrote: Greg KH gre...@linuxfoundation.org writes: 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.

Re: git archve --format=tar output changed from 1.8.1 to 1.8.2.1

2013-02-03 Thread Greg KH
On Thu, Jan 31, 2013 at 10:16:27AM -0800, Junio C Hamano wrote: Greg KH gre...@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

Re: git archve --format=tar output changed from 1.8.1 to 1.8.2.1

2013-02-03 Thread Greg KH
On Thu, Jan 31, 2013 at 07:33:52PM +0100, René Scharfe wrote: Am 31.01.2013 18:28, schrieb Greg KH: I tracked this down to commit 22f0dcd9634a818a0c83f23ea1a48f2d620c0546 (archive-tar: split long paths more carefully). The diff of a hex dump of the tar archives shows the following

Re: git archve --format=tar output changed from 1.8.1 to 1.8.2.1

2013-02-03 Thread Greg KH
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

Re: git archve --format=tar output changed from 1.8.1 to 1.8.2.1

2013-02-03 Thread Junio C Hamano
Greg KH gre...@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

Re: git archve --format=tar output changed from 1.8.1 to 1.8.2.1

2013-01-31 Thread Junio C Hamano
Greg KH gre...@linuxfoundation.org writes: The way we upload the Linux kernel to kernel.org involves creating a tar archive, signing the archive, and then just uploading the signature. The server then checks out the repo based on the tag, generates the tar archive and checks the signature to

Re: git archve --format=tar output changed from 1.8.1 to 1.8.2.1

2013-01-31 Thread Greg KH
On Thu, Jan 31, 2013 at 09:32:12AM -0800, Junio C Hamano wrote: Greg KH gre...@linuxfoundation.org writes: The way we upload the Linux kernel to kernel.org involves creating a tar archive, signing the archive, and then just uploading the signature. The server then checks out the repo

Re: git archve --format=tar output changed from 1.8.1 to 1.8.2.1

2013-01-31 Thread Konstantin Ryabitsev
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

Re: git archve --format=tar output changed from 1.8.1 to 1.8.2.1

2013-01-31 Thread René Scharfe
Am 31.01.2013 18:28, schrieb Greg KH: I tracked this down to commit 22f0dcd9634a818a0c83f23ea1a48f2d620c0546 (archive-tar: split long paths more carefully). The diff of a hex dump of the tar archives shows the following difference: --- old_git_archive 2013-01-31 17:31:24.466343388 +0100