Re: What's cooking in git.git (Jan 2016, #04; Wed, 20)

[Junio C Hamano <gitster@pobox.com>]

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

> On Wed, 20 Jan 2016, Junio C Hamano wrote:
>
>> * bb/merge-marker-crlf (2015-11-24) 1 commit
>>  - merge-file: consider core.crlf when writing merge markers
>> 
>>  Write out merge markers using system end-of-line convention.
>> 
>>  Waiting for a re-roll to handle gitattributes.
>>  ($gmane/281701)
>
> For the record, it is $gmane/281700.

Not quite; 281701 is a more correct reference than 281700 at two
counts.  One of them is not your fault, as I haven't explained what
these references _mean_.  These references are not about "Go there
to get the original e-mail of the patch."  And 281700 is wrong by
being off by 100, as the original patch is $gmane/281600, even if
these references meant what you thought they did ;-).

These are "Go there to learn more about the reason behind the
statement above."  I (or anybody) visits 281701 and sees an
unresolved comment in the discussion thread to realize that the
maintainer is doing the right thing by not moving the version that
is queued forward prematurely before issues are resolved.

> I will send out a replacement series shortly.

Thanks.