On 11/13/2018 10:24 PM, Junio C Hamano wrote:
Jonathan Nieder writes:
We cannot change the past, but for index extensions of the future,
there is a straightforward improvement: silence that message except
when tracing. This way, the message is still available when
debugging, but in everyda
Jonathan Nieder writes:
> We cannot change the past, but for index extensions of the future,
> there is a straightforward improvement: silence that message except
> when tracing. This way, the message is still available when
> debugging, but in everyday use it does not show up so (once most Git
On 11/12/2018 7:40 PM, Jonathan Nieder wrote:
Documentation/technical/index-format explains:
4-byte extension signature. If the first byte is 'A'..'Z' the
extension is optional and can be ignored.
This allows gracefully introducing a new index extension without
having to rely on
Jonathan Nieder writes:
> We almost obey that convention, but there is a problem: when
> encountering an unrecognized optional extension, we write
>
> ignoring FNCY extension
>
> to stderr, which alarms users.
Then the same comment as 2/3 applies to this step.
Documentation/technical/index-format explains:
4-byte extension signature. If the first byte is 'A'..'Z' the
extension is optional and can be ignored.
This allows gracefully introducing a new index extension without
having to rely on all readers having support for it. Mandatory
extensi
5 matches
Mail list logo