Thread (21 messages) flat view 21 messages, 7 authors, 2016-06-15

Re: [PATCH] provide advance warning of some future pack default changes

From: Nicolas Pitre <hidden>
Date: 2016-06-15 22:43:59

Possibly related (same subject, not in this thread)

On Fri, 14 Dec 2007, Joel Becker wrote:
On Fri, Dec 14, 2007 at 05:46:14PM -0500, Nicolas Pitre wrote:
quoted
On Fri, 14 Dec 2007, Joel Becker wrote:
quoted
On Fri, Dec 14, 2007 at 05:34:49PM -0500, Nicolas Pitre wrote:
quoted
But you know what? repositories with the change affecting 1.4.4 users 
are _already_ out there and no one complained recently.  Anyone pushing 
	I did, as did people I work with.  It's on git-list, even.  I'm
pretty sure it corrupted too.
Could you please give me a reference to such message, so to verify that 
we're actually talking about the same thing?
	The relevant message is:

Message-ID: [off-list ref]

See the paragraphs at the bottom.  The thread, started by me, begins
with:

Message-ID: [off-list ref]
OK.  From those emails Junio forwarded to me, I don't see any case for 
actual _corruptions_.  Git does indeed refuse to work with unknown pack 
index or unknown objects in a pack.  Really old versions were not overly 
clueful as to why they refused to work, but they should never corrupt a 
pack which, for all purposes, is always read-only anyway.


Nicolas
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help