From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Make find_commit_subject() more robust
Date: Wed, 22 Jun 2016 11:03:51 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1606221041320.10382@virtualbox> (raw)
In-Reply-To: <xmqqziqent0e.fsf@gitster.mtv.corp.google.com>
Hi Junio,
On Tue, 21 Jun 2016, Junio C Hamano wrote:
> Your patch introduces a similar loop with similar (but different)
> purpose:
>
> while (*p == '\n')
> p++;
>
> which would have been helped if there were a helper with an
> opposite function, i.e.
>
> p = strcchrnul(p, '\n');
>
> i.e. "give me the pointer to the first byte that is not '\n', or EOS".
>
> But there is no such thing. Although p += strcspn(p, "\n") is a
> possibility, that somehow feels a bit odd. And that is why I did
> not hint any existing function and said "might want to find".
Sure. And strcspn() is less efficient than the loop if you already know
that the second parameter contains only a single character.
> HOWEVER.
>
> Stepping back a bit, I think what we actually want is
>
> p = skip_blank_lines(p);
>
> that skips any and all blank lines, including an empty line that
> consists of all whitespace.
My original aim was to make find_commit_subject() consistent with the
pretty-printing machinery. I failed to realize that skip_blank_lines()
does more than skipping empty lines, so let me re-roll the patch.
Ciao,
Dscho
next prev parent reply other threads:[~2016-06-22 9:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-18 13:12 [PATCH] Make find_commit_subject() more robust Johannes Schindelin
2016-06-20 19:35 ` Junio C Hamano
2016-06-21 12:03 ` Johannes Schindelin
2016-06-21 21:15 ` Junio C Hamano
2016-06-22 9:03 ` Johannes Schindelin [this message]
2016-06-21 12:43 ` [PATCH v2] " Johannes Schindelin
2016-06-21 20:34 ` Junio C Hamano
2016-06-22 9:34 ` [PATCH v3 0/2] Make find_commit_subject() consistent with --format=%s Johannes Schindelin
2016-06-22 9:34 ` [PATCH v3 1/2] Make the skip_empty_lines() function public Johannes Schindelin
2016-06-22 9:34 ` [PATCH v3 2/2] Make find_commit_subject() more robust Johannes Schindelin
2016-06-22 17:21 ` [PATCH v3 0/2] Make find_commit_subject() consistent with --format=%s Junio C Hamano
2016-06-22 20:20 ` Johannes Schindelin
2016-06-22 20:20 ` [PATCH v4 " Johannes Schindelin
2016-06-22 20:20 ` [PATCH v4 1/2] Make the skip_blank_lines() function public Johannes Schindelin
2016-06-22 20:20 ` [PATCH v4 2/2] Make find_commit_subject() more robust Johannes Schindelin
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=alpine.DEB.2.20.1606221041320.10382@virtualbox \
--to=johannes.schindelin@gmx.de \
--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 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 NNTP newsgroup(s).