Re: Draft of Git Rev News edition 33

From: Junio C Hamano <gitster@pobox.com>
Date: Nov 21, 2017, 13:12 UTC
Message-ID: <xmqqvai3zsge.fsf@gitster.mtv.corp.google.com>
In-Reply-To: <CAP8UFD0dN2V5GVokvMD-XLDEhPVJrE=m3h8oM5VC_Lq6x3=9=A@mail.gmail.com>

Christian Couder <christian.couder@gmail.com> writes:

Show 13 quoted lines

> On Tue, Nov 21, 2017 at 2:10 AM, Jonathan Nieder <jrnieder@gmail.com> wrote:
>>
>> That said, I believe that the gitattributes(5) manpage does an okay
>> job of covering this and that that thread came to a clear conclusion:
>>
>>   https://public-inbox.org/git/20171026203046.fu3z5ngnw7hckfrn@aiede.mtv.corp.google.com/
>>
>> I commented at [1] that I found the conclusion of the rev news entry
>> misleading and confusing but it doesn't appear that there is anything
>> I can do about that.
>
> Well, you could have provided a pull request or otherwise suggested
> what you think would be a better conclusion for the article and why.

I just re-read the sub-thread Jonathan pointed at, and to me it does look like the original request was adequately addressed and talk has concluded at around that article.

I somehow was hoping that Jonathan's citing the above URL is a suggestion enough for the editors, especially given that the announcement for the draft invites a reply to this thread.

> Perhaps nothing was missed, but as the issue is complex, it is just
> difficult to explain and summarize it in a good way.

Perhaps you want to take a bit more time between a draft to the final publication? I've often wondered if the time between a draft announcement and the release is too short for those who understand the discussions on the list well enough to give useful input to help editors regurgitate the issues to arrive at a clear summary article.