From: Junio C Hamano <gitster@pobox.com>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: Git List <git@vger.kernel.org>,
Jonathan Nieder <jrnieder@gmail.com>, Jeff King <peff@peff.net>,
Daniel Barkalow <barkalow@iabervon.org>,
Christian Couder <chriscool@tuxfamily.org>
Subject: Re: [PATCH 4/6] revert: Make commit descriptions in insn sheet optional
Date: Mon, 10 Oct 2011 10:54:50 -0700 [thread overview]
Message-ID: <7vwrccn34l.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <1318095407-26429-5-git-send-email-artagnon@gmail.com> (Ramkumar Ramachandra's message of "Sat, 8 Oct 2011 23:06:45 +0530")
Ramkumar Ramachandra <artagnon@gmail.com> writes:
> Change the instruction sheet format subtly so that a description of
> the commit after the object name is optional. As a result, an
> instruction sheet like this is now perfectly valid:
>
> pick 35b0426
> pick fbd5bbcbc2e
> pick 7362160f
>
> Suggested-by: Jonathan Nieder <jrnieder@gmail.com>
> Acked-by: Jonathan Nieder <jrnieder@gmail.com>
> Signed-off-by: Ramkumar Ramachandra <artagnon@gmail.com>
> ---
> builtin/revert.c | 19 ++++++++-----------
> t/t3510-cherry-pick-sequence.sh | 14 ++++++++++++++
> 2 files changed, 22 insertions(+), 11 deletions(-)
>
> diff --git a/builtin/revert.c b/builtin/revert.c
> index 6451089..aa6c34e 100644
> --- a/builtin/revert.c
> +++ b/builtin/revert.c
> @@ -692,26 +692,23 @@ static struct commit *parse_insn_line(char *start, struct replay_opts *opts)
> unsigned char commit_sha1[20];
> char sha1_abbrev[40];
> enum replay_action action;
> - int insn_len = 0;
> - char *p, *q;
> + const char *p, *q;
>
> + p = start;
> if (!prefixcmp(start, "pick ")) {
> action = CHERRY_PICK;
> - insn_len = strlen("pick");
> - p = start + insn_len + 1;
> + p += strlen("pick ");
> } else if (!prefixcmp(start, "revert ")) {
> action = REVERT;
> - insn_len = strlen("revert");
> - p = start + insn_len + 1;
> + p += strlen("revert ");
> } else
> return NULL;
>
> - q = strchr(p, ' ');
> - if (!q || q - p + 1 > sizeof(sha1_abbrev))
> + q = p + strcspn(p, " \n");
> + if (q - p + 1 > sizeof(sha1_abbrev))
> return NULL;
> - q++;
> -
> - strlcpy(sha1_abbrev, p, q - p);
> + memcpy(sha1_abbrev, p, q - p);
> + sha1_abbrev[q - p] = '\0';
Since this is a part of clean-up series...
Do you even need to have a sha1_abbrev[] local array that is limited to 40
bytes here? The incoming _line_ is not "const char *start", so you should
at least be able to temporarily terminate the commit object name with NUL
(while remembering what byte there was before), give it to get_sha1(), and
then restore the byte at the end before returning from this function.
A bonus point would be to introduce a variant of get_sha1() that can take
(a pointer + len) not (a pointer to NUL terminated string). While I think
that would be a right thing to do in the longer term, it is outside of the
scope of this series.
next prev parent reply other threads:[~2011-10-10 17:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-08 17:36 [PATCH 0/6] Sequencer fixups mini-series Ramkumar Ramachandra
2011-10-08 17:36 ` [PATCH 1/6] revert: Free memory after get_message call Ramkumar Ramachandra
2011-10-08 17:36 ` [PATCH 2/6] revert: Simplify getting commit subject Ramkumar Ramachandra
2011-10-08 17:36 ` [PATCH 3/6] revert: Fix buffer overflow in insn sheet parser Ramkumar Ramachandra
2011-10-08 17:36 ` [PATCH 4/6] revert: Make commit descriptions in insn sheet optional Ramkumar Ramachandra
2011-10-10 17:54 ` Junio C Hamano [this message]
2011-10-12 21:05 ` Junio C Hamano
2011-10-17 10:06 ` Ramkumar Ramachandra
2011-10-08 17:36 ` [PATCH 5/6] revert: Allow mixed pick and revert instructions Ramkumar Ramachandra
2011-10-08 17:36 ` [PATCH 6/6] revert: Simplify passing command-line arguments around Ramkumar Ramachandra
2011-10-09 2:14 ` Tay Ray Chuan
2011-10-09 8:28 ` Ramkumar Ramachandra
2011-10-09 8:53 ` Jonathan Nieder
2011-10-09 9:04 ` Ramkumar Ramachandra
2011-10-09 9:24 ` Jonathan Nieder
2011-10-17 10:10 ` Ramkumar Ramachandra
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=7vwrccn34l.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=artagnon@gmail.com \
--cc=barkalow@iabervon.org \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--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 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).