git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Christian Couder <christian.couder@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Jonathan Nieder" <jrnieder@gmail.com>,
	"Yubin Ruan" <ablacktshirt@gmail.com>, git <git@vger.kernel.org>,
	"Thomas Ferris Nicolaisen" <tfnico@gmail.com>,
	"Jakub Narebski" <jnareb@gmail.com>,
	"Markus Jansen" <mja@jansen-preisler.de>,
	"Jeff King" <peff@peff.net>,
	"Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
	"Stefan Beller" <sbeller@google.com>,
	"Оля Тележная" <olyatelezhnaya@gmail.com>,
	"Johannes Sixt" <j6t@kdbg.org>,
	"Torsten Bögershausen" <tboegi@web.de>,
	"Lars Schneider" <larsxschneider@gmail.com>,
	"Jacob Keller" <jacob.keller@gmail.com>,
	"Phillip Wood" <phillip.wood@talktalk.net>,
	"Ross Kabus" <rkabus@aerotech.com>,
	"Henry Kleynhans" <hkleynhans@bloomberg.net>,
	"Charles Bailey" <charles@hashpling.org>,
	"Thomas Gummerer" <t.gummerer@gmail.com>
Subject: Re: Draft of Git Rev News edition 33
Date: Tue, 21 Nov 2017 14:41:18 +0100	[thread overview]
Message-ID: <CAP8UFD3QdwnN3Mrc5Xx3C0ROxhm6eS9OFuiVxFTUSrXYknTOWA@mail.gmail.com> (raw)
In-Reply-To: <xmqqvai3zsge.fsf@gitster.mtv.corp.google.com>

On Tue, Nov 21, 2017 at 2:12 PM, Junio C Hamano <gitster@pobox.com> wrote:
> Christian Couder <christian.couder@gmail.com> writes:
>
>> 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.

DId you also read https://github.com/git/git.github.io/issues/262?

I think I have tried to properly answer Jonathan's feedback there too.
Especially I wrote a pull request with a different conclusion
(https://github.com/git/git.github.io/pull/265) and asked Jonathan if
that was better, but so far got no answer.

>> 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.

If it would take a really long time for "those who understand the
discussions on the list well enough to give useful input", can you
imagine how long it would take to write articles in the first place?

I try to write the articles in less than 2 days, so I think 2 days
should also be enough for people to provide useful input on the
articles.
Also I have tried at times to give one more day for people to provide
feedback (or more content) following you suggestion. But when I did
that, I have seen no change in the amount of feedback (or content)
provided.

  reply	other threads:[~2017-11-21 13:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-20  8:33 Draft of Git Rev News edition 33 Christian Couder
2017-11-21  0:38 ` Yubin Ruan
2017-11-21  1:10   ` Jonathan Nieder
2017-11-21  8:17     ` Christian Couder
2017-11-21 13:12       ` Junio C Hamano
2017-11-21 13:41         ` Christian Couder [this message]
2017-11-22  1:28           ` Junio C Hamano
2017-11-22  1:41       ` Jonathan Nieder

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAP8UFD3QdwnN3Mrc5Xx3C0ROxhm6eS9OFuiVxFTUSrXYknTOWA@mail.gmail.com \
    --to=christian.couder@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=ablacktshirt@gmail.com \
    --cc=charles@hashpling.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=hkleynhans@bloomberg.net \
    --cc=j6t@kdbg.org \
    --cc=jacob.keller@gmail.com \
    --cc=jnareb@gmail.com \
    --cc=jrnieder@gmail.com \
    --cc=larsxschneider@gmail.com \
    --cc=mja@jansen-preisler.de \
    --cc=olyatelezhnaya@gmail.com \
    --cc=peff@peff.net \
    --cc=phillip.wood@talktalk.net \
    --cc=rkabus@aerotech.com \
    --cc=sbeller@google.com \
    --cc=t.gummerer@gmail.com \
    --cc=tboegi@web.de \
    --cc=tfnico@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).