From: Junio C Hamano <gitster@pobox.com>
To: Christian Couder <chriscool@tuxfamily.org>
Cc: git@vger.kernel.org, Jeff King <peff@peff.net>,
Michael Haggerty <mhagger@alum.mit.edu>,
Jakub Narebski <jnareb@gmail.com>,
Eric Sunshine <sunshine@sunshineco.com>
Subject: Re: [PATCH v5 6/7] replace: remove signature when using --graft
Date: Wed, 02 Jul 2014 14:19:26 -0700 [thread overview]
Message-ID: <xmqqpphnfogx.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <20140628181117.5687.38249.chriscool@tuxfamily.org> (Christian Couder's message of "Sat, 28 Jun 2014 20:11:15 +0200")
Christian Couder <chriscool@tuxfamily.org> writes:
> It could be misleading to keep a signature in a
> replacement commit, so let's remove it.
>
> Note that there should probably be a way to sign
> the replacement commit created when using --graft,
> but this can be dealt with in another commit or
> patch series.
Both paragraphs read very sensibly.
>
> Signed-off-by: Christian Couder <chriscool@tuxfamily.org>
> ---
> builtin/replace.c | 5 +++++
> commit.c | 34 ++++++++++++++++++++++++++++++++++
> commit.h | 2 ++
> 3 files changed, 41 insertions(+)
>
> diff --git a/builtin/replace.c b/builtin/replace.c
> index ad47237..000db65 100644
> --- a/builtin/replace.c
> +++ b/builtin/replace.c
> @@ -344,6 +344,11 @@ static int create_graft(int argc, const char **argv, int force)
>
> replace_parents(&buf, argc, argv);
>
> + if (remove_signature(&buf))
> + warning(_("the original commit '%s' has a gpg signature.\n"
> + "It will be removed in the replacement commit!"),
Hmmm... does the second line of this message start with the usual
"warning:" prefix?
> diff --git a/commit.c b/commit.c
> index fb7897c..54e157d 100644
> --- a/commit.c
> +++ b/commit.c
> @@ -1177,6 +1177,40 @@ int parse_signed_commit(const struct commit *commit,
> return saw_signature;
> }
>
> +int remove_signature(struct strbuf *buf)
> +{
> + const char *line = buf->buf;
> + const char *tail = buf->buf + buf->len;
> + int in_signature = 0;
> + const char *sig_start = NULL;
> + const char *sig_end = NULL;
> +
> + while (line < tail) {
> + const char *next = memchr(line, '\n', tail - line);
> + next = next ? next + 1 : tail;
This almost makes me wonder if we want something similar to
strchrnul() we use for NUL-terminated strings, and I suspect that
you would find more instances by running "git grep -A2 memchr".
I don't know what such a helper function should be named, though.
Certainly not "memchrnul()".
> +
> + if (in_signature && line[0] == ' ')
> + sig_end = next;
> + else if (starts_with(line, gpg_sig_header) &&
> + line[gpg_sig_header_len] == ' ') {
> + sig_start = line;
> + sig_end = next;
> + in_signature = 1;
> + } else {
> + if (*line == '\n')
> + /* dump the whole remainder of the buffer */
> + next = tail;
> + in_signature = 0;
> + }
> + line = next;
> + }
> +
> + if (sig_start)
> + strbuf_remove(buf, sig_start - buf->buf, sig_end - sig_start);
If there are two instances of gpg_sig, this will remove only the
last one, but there is no chance both signatures of such a commit
can validate OK, and we won't be losing something in between anyway,
so it should be fine.
> + return sig_start != NULL;
> +}
> +
> static void handle_signed_tag(struct commit *parent, struct commit_extra_header ***tail)
> {
> struct merge_remote_desc *desc;
> diff --git a/commit.h b/commit.h
> index 2e1492a..4234dae 100644
> --- a/commit.h
> +++ b/commit.h
> @@ -327,6 +327,8 @@ struct commit *get_merge_parent(const char *name);
>
> extern int parse_signed_commit(const struct commit *commit,
> struct strbuf *message, struct strbuf *signature);
> +extern int remove_signature(struct strbuf *buf);
> +
> extern void print_commit_list(struct commit_list *list,
> const char *format_cur,
> const char *format_last);
next prev parent reply other threads:[~2014-07-02 21:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-28 18:11 [PATCH v5 0/7] Add --graft option to git replace Christian Couder
2014-06-28 18:11 ` [PATCH v5 1/7] replace: add --graft option Christian Couder
2014-06-28 18:11 ` [PATCH v5 2/7] replace: add test for --graft Christian Couder
2014-07-02 20:49 ` Junio C Hamano
2014-07-03 13:39 ` Christian Couder
2014-07-03 18:45 ` Junio C Hamano
2014-06-28 18:11 ` [PATCH v5 3/7] Documentation: replace: add --graft option Christian Couder
2014-06-28 18:11 ` [PATCH v5 4/7] contrib: add convert-grafts-to-replace-refs.sh Christian Couder
2014-06-28 18:11 ` [PATCH v5 5/7] replace: refactor replacing parents Christian Couder
2014-07-02 21:05 ` Junio C Hamano
2014-07-03 13:42 ` Christian Couder
2014-06-28 18:11 ` [PATCH v5 6/7] replace: remove signature when using --graft Christian Couder
2014-07-02 21:19 ` Junio C Hamano [this message]
2014-07-03 14:09 ` Christian Couder
2014-06-28 18:11 ` [PATCH v5 7/7] replace: add test for --graft with signed commit Christian Couder
2014-07-02 21:22 ` Junio C Hamano
2014-07-03 14:17 ` 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=xmqqpphnfogx.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=mhagger@alum.mit.edu \
--cc=peff@peff.net \
--cc=sunshine@sunshineco.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.