All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Michael Haggerty <mhagger@alum.mit.edu>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 5/5] RelNotes: wordsmithing
Date: Thu, 23 Apr 2015 08:38:18 -0700	[thread overview]
Message-ID: <xmqq618mdfdh.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <5538E9F3.7040702@alum.mit.edu> (Michael Haggerty's message of "Thu, 23 Apr 2015 14:47:47 +0200")

Michael Haggerty <mhagger@alum.mit.edu> writes:

> On 04/23/2015 02:27 PM, Michael Haggerty wrote:
>> Make many textual tweaks to the 2.4.0 release notes.
>> 
>> Signed-off-by: Michael Haggerty <mhagger@alum.mit.edu>
>> ---
>>  Documentation/RelNotes/2.4.0.txt | 336 ++++++++++++++++++++-------------------
>>  1 file changed, 172 insertions(+), 164 deletions(-)
>> 
>> diff --git a/Documentation/RelNotes/2.4.0.txt b/Documentation/RelNotes/2.4.0.txt
>> index 7b23ca3..cde64be 100644
>> --- a/Documentation/RelNotes/2.4.0.txt
>> +++ b/Documentation/RelNotes/2.4.0.txt
>> [...]
>
> Oh, I just noticed that many of the same blurbs appear in the release
> notes for the maintenance versions. Once there is agreement on how many
> of the changes to accept, the analogous changes should probably be made
> in those other files.

Thanks.

FYI, these days the same text appears in

 (1) the topic description in "What's cooking";
 (2) the merge commit for the topic when it is merged to 'next';
 (3) the merge commit for the topic when it is merged to 'master';
 (4) Release notes for the 'master' and 'maint', when it is merged.

So the best time to catch mistakes and to rephrase it is when you
see something questionable in "What's cooking", ideally before it
hits 'next', before it hits 'master'.

      reply	other threads:[~2015-04-23 15:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-23 12:27 [PATCH 0/5] Tweak the 2.4.0 release notes and related docs Michael Haggerty
2015-04-23 12:27 ` [PATCH 1/5] status: document the -v/--verbose option Michael Haggerty
2015-04-23 18:26   ` Junio C Hamano
2015-04-23 12:27 ` [PATCH 2/5] git tag: mention versionsort.prereleaseSuffix in manpage Michael Haggerty
2015-04-23 18:28   ` Junio C Hamano
2015-04-23 12:27 ` [PATCH 3/5] RelNotes: correct name of versionsort.prereleaseSuffix Michael Haggerty
2015-04-23 18:29   ` Junio C Hamano
2015-04-23 12:27 ` [PATCH 4/5] RelNotes: refer to the rebase -i "todo list", not "insn sheet" Michael Haggerty
2015-04-23 12:27 ` [PATCH 5/5] RelNotes: wordsmithing Michael Haggerty
2015-04-23 12:47   ` Michael Haggerty
2015-04-23 15:38     ` Junio C Hamano [this message]

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

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

  git send-email \
    --in-reply-to=xmqq618mdfdh.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=mhagger@alum.mit.edu \
    /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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.