From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 0/6] 2.14 RelNotes improvements
Date: Fri, 21 Jul 2017 13:03:39 +0200 [thread overview]
Message-ID: <87pocuoxv8.fsf@gmail.com> (raw)
In-Reply-To: <xmqqshhqkfrs.fsf@gitster.mtv.corp.google.com>
On Thu, Jul 20 2017, Junio C. Hamano jotted:
> Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
>
>> Here's a few patches to improve the relnotes. I started just writing
>> 6/6 since I think (I don't care about the wording) that we should in
>> some way mention the items in the list in the 6/6 commit message.
>>
>> Along the way I noticed a few more missing things.
>>
>> Ævar Arnfjörð Bjarmason (6):
>> RelNotes: mention "log: add -P as a synonym for --perl-regexp"
>> RelNotes: mention "log: make --regexp-ignore-case work with
>> --perl-regexp"
>> RelNotes: mention "sha1dc: optionally use sha1collisiondetection as a
>> submodule"
>> RelNotes: mention that PCRE v2 exposes the same syntax
>> RelNotes: remove duplicate mention of PCRE v2
>> RelNotes: add more notes about PCRE in 2.14
>
> Thanks. 1-3/6 went straight to 'master'. I am not outright
> rejecting the remainder, but I do not think these are release notes
> material---if they need to be told, they should be in a part of the
> regular documentation, and I suspect that they already are in your
> series.
Thanks. I agree that 4-6 are better left to the docs. I wasn't very
familiar with the format of the release notes / what you preferref to
list there & how.
I'll integrate what 6/6 mentions with my nascent gitperformance.txt
series.
next prev parent reply other threads:[~2017-07-21 11:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-13 23:43 [ANNOUNCE] Git v2.14.0-rc0 Junio C Hamano
2017-07-14 23:17 ` Ævar Arnfjörð Bjarmason
2017-07-15 4:09 ` Christian Couder
2017-07-15 10:09 ` Ævar Arnfjörð Bjarmason
2017-07-17 20:41 ` Junio C Hamano
2017-07-18 20:03 ` Junio C Hamano
2017-07-20 14:19 ` [PATCH 0/6] 2.14 RelNotes improvements Ævar Arnfjörð Bjarmason
2017-07-20 20:35 ` Junio C Hamano
2017-07-21 11:03 ` Ævar Arnfjörð Bjarmason [this message]
2017-07-20 14:19 ` [PATCH 1/6] RelNotes: mention "log: add -P as a synonym for --perl-regexp" Ævar Arnfjörð Bjarmason
2017-07-20 14:19 ` [PATCH 2/6] RelNotes: mention "log: make --regexp-ignore-case work with --perl-regexp" Ævar Arnfjörð Bjarmason
2017-07-20 14:19 ` [PATCH 3/6] RelNotes: mention "sha1dc: optionally use sha1collisiondetection as a submodule" Ævar Arnfjörð Bjarmason
2017-07-20 14:19 ` [PATCH 4/6] RelNotes: mention that PCRE v2 exposes the same syntax Ævar Arnfjörð Bjarmason
2017-07-20 15:24 ` Junio C Hamano
2017-07-20 14:19 ` [PATCH 5/6] RelNotes: remove duplicate mention of PCRE v2 Ævar Arnfjörð Bjarmason
2017-07-20 15:26 ` Junio C Hamano
2017-07-20 14:19 ` [PATCH 6/6] RelNotes: add more notes about PCRE in 2.14 Ævar Arnfjörð Bjarmason
2017-07-20 19:11 ` Junio C Hamano
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=87pocuoxv8.fsf@gmail.com \
--to=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
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.