From: Junio C Hamano <gitster@pobox.com>
To: Antoine Pelisse <apelisse@gmail.com>
Cc: Christian Couder <chriscool@tuxfamily.org>,
Jonathan Nieder <jrnieder@gmail.com>, git <git@vger.kernel.org>,
apenwarr@gmail.com,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Jeff King <peff@peff.net>, Max Horn <max@quendi.de>,
ae@op5.se
Subject: Re: [PATCH v4 2/2] Rename suffixcmp() to ends_with() and invert its result
Date: Tue, 19 Nov 2013 14:28:08 -0800 [thread overview]
Message-ID: <xmqq4n7881s7.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <CALWbr2yG7XOhuZa9bf6sXRV=m49dTPNyPZ9JUU2-_2G8ZJsCTg@mail.gmail.com> (Antoine Pelisse's message of "Tue, 19 Nov 2013 22:32:56 +0100")
Antoine Pelisse <apelisse@gmail.com> writes:
> On Tue, Nov 19, 2013 at 10:04 PM, Christian Couder
> <chriscool@tuxfamily.org> wrote:
>> To avoid spamming the list again, I am going to send the following
>> patches from the 86 patch long series to replace prefixcmp() with
>> starts_with():
>>
>> [PATCH v2 00/86] replace prefixcmp() with starts_with()
>> [PATCH v2 01/86] strbuf: add starts_with() to be used instead of prefixcmp()
>> [PATCH v2 02/86] diff: replace prefixcmp() with starts_with()
>> [PATCH v2 08/86] transport*: replace prefixcmp() with starts_with()
>> [PATCH v2 40/86] environment: replace prefixcmp() with starts_with()
>> [PATCH v2 86/86] strbuf: remove prefixcmp() as it has been replaced with starts_with()
>>
>> If there are no problems with them, then I will suppose that most of
>> the patches are ok and probably send them all unless I am asked not
>> to.
>
> I'm not exactly sure I understand the point of not squashing all those
> patches together ?
> It's not like one is going without the others, or that the commit
> message provides some new information (except for the name of the
> file, but that is not very relevant either). The downside is that it's
> _many_ messages to bypass when reading mails from small-screen devices
> :-)
The only plausible reason I could think of is to avoid clashing with
topics in-flight, but then the approach to produce per-file patch is
not perfect for that purpose, either, when more than one topic in
flight touch the same file at different places.
I'd say probably the best organization would be something like:
* A set of clean-up patches to normalize oddball usages of existing
functions (e.g. normalize 'prefixcmp(a,b) != 0' in some file(s)
to 'prefixcmp(a,b)');
* A single patch to introduce the new function(s), to be applied on
top of 1.8.5;
* A large patch to convert all uses of prefixcmp to starts_with and
suffixcmp to ends_with in the 1.8.5 codebase;
* A patch for each topic in flight to convert newly introduced
prefixcmp/suffixcmp to starts_with/ends_with, to be applied after
the topic graduates to 'master' after 1.8.5; and then finally
* A separate patch to remove prefixcmp and suffixcmp, to be applied
after _all_ in-flight topic has graduated to 'master'.
next prev parent reply other threads:[~2013-11-19 22:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-17 8:39 [PATCH v4 2/2] Rename suffixcmp() to ends_with() and invert its result Christian Couder
2013-11-19 19:13 ` Jonathan Nieder
2013-11-19 21:04 ` Christian Couder
2013-11-19 21:32 ` Antoine Pelisse
2013-11-19 22:28 ` Junio C Hamano [this message]
2013-11-21 7:32 ` Christian Couder
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=xmqq4n7881s7.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=ae@op5.se \
--cc=apelisse@gmail.com \
--cc=apenwarr@gmail.com \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=max@quendi.de \
--cc=peff@peff.net \
/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.