Re: warning in tree xxx: contains zero-padded file modes
- From
Jeff King <peff@peff.net>
- Date
- Feb 6, 2017, 20:32 UTC
- Message-ID
- <20170206203214.5y6ynn5co7davtrj@sigill.intra.peff.net>
- In-Reply-To
- <CAJZjrdWq+xSEoTypA_hWdQJgioGOHJd3V7djeQ0YxpzvhuoM=g@mail.gmail.com>
On Mon, Feb 06, 2017 at 02:23:37PM -0600, Samuel Lijin wrote:
> >> There are some discussions in the past [1] [2] about this. > > I think you forgot to link to [2] :p
I think the [1] [2] there were recursive quotes from Duy's email. Those footnotes were:
[1] http://public-inbox.org/git/%3CCAEBDL5W3DL0v=TusuB7Vg-4bWdAJh5d2Psc1N0Qe+KK3bZH3=Q@mail.gmail.com%3E/ [2] http://public-inbox.org/git/%3C20100326215600.GA10910@spearce.org%3E/
> The linked issue on bugs.debian.org has seen activity recently, which > is the main reason I mentioned it separately as still relevant: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743227
Yeah. I think that's not quite solvable with Git as we have it now. We have fsck.* and receive.fsck.* to tweak severity levels, but no matching fetch.fsck.* for handling a push (and presumably a transfer.fsck.* to cover both fetching and pushing). So there's a potential patch series for anybody interested.
-Peff