From: Junio C Hamano <gitster@pobox.com>
To: Matthieu Moy <Matthieu.Moy@imag.fr>
Cc: git@vger.kernel.org, remi.lespinet@ensimag.grenoble-inp.fr,
guillaume.pages@ensimag.grenoble-inp.fr,
louis--alexandre.stuber@ensimag.grenoble-inp.fr,
antoine.delaite@ensimag.grenoble-inp.fr
Subject: Re: [PATCH v5 3/4] status: give more information during rebase -i
Date: Wed, 01 Jul 2015 09:18:56 -0700 [thread overview]
Message-ID: <xmqq4mlnc0lr.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <1435739433-18853-3-git-send-email-Matthieu.Moy@imag.fr> (Matthieu Moy's message of "Wed, 1 Jul 2015 10:30:32 +0200")
Matthieu Moy <Matthieu.Moy@imag.fr> writes:
> +/*
> + * Turn
> + * pick d6a2f0303e897ec257dd0e0a39a5ccb709bc2047 some message
> + * into
> + * pick d6a2f03 some message
> + */
> +static void abbrev_sha1_in_line(struct strbuf *line)
> +{
> + struct strbuf **split;
> + int i;
> +
> + if (starts_with(line->buf, "exec ") ||
> + starts_with(line->buf, "x "))
> + return;
> +
> + split = strbuf_split_max(line, ' ', 3);
> + if (split[0] && split[1]) {
> + unsigned char sha1[20];
> + const char *abbrev;
> +
> + /*
> + * strbuf_split_max left a space. Trim it and re-add
> + * it after abbreviation.
> + */
> + strbuf_trim(split[1]);
> + if (!get_sha1(split[1]->buf, sha1)) {
> + abbrev = find_unique_abbrev(sha1, DEFAULT_ABBREV);
> + strbuf_reset(split[1]);
> + strbuf_addf(split[1], "%s ", abbrev);
> + }
... else?
That is, "we thought there would be a full SHA-1, but it turns out
that there wasn't, so we keep split[1] as-is" would need to add the
space back, no? Perhaps be more strict and do this instead (without
leading strbuf_trim):
if (!get_sha1_hex(split[1]->buf, sha1) &&
!strcmp(split[1]->buf + 40, " ") {
replace split[1] with "%s " abbrev
}
> + strbuf_reset(line);
> + for (i = 0; split[i]; i++)
> + strbuf_addstr(line, split[i]->buf);
> + }
> + for (i = 0; split[i]; i++)
> + strbuf_release(split[i]);
> +
> +}
> +
> +static void read_rebase_todolist(const char *fname, struct string_list *lines)
> +{
> + struct strbuf line = STRBUF_INIT;
> + FILE *f = fopen(git_path(fname), "r");
> +
> + if (!f)
> + die_errno("Could not open file %s for reading", git_path(fname));
> + while (!strbuf_getline(&line, f, '\n')) {
> + stripspace(&line, 1);
stripspace() is meant to be used for multi-line input (e.g. it
collapses a multi-line paragraph break into one blank line) and it
does not look a good fit in a loop that goes line-by-line. As you
call (and you have to, because stripspace() fixes the incomplete
line by adding LF at the end) rtrim() immediately afterward, this
call is done only for removing comments (in other words, trailing
whitespaces are removed without the call to stripspace() anyway).
> + /* Remove trailing \n */
> + strbuf_rtrim(&line);
> + abbrev_sha1_in_line(&line);
> + string_list_append(lines, line.buf);
> + }
> + string_list_remove_empty_items(lines, 1);
> +}
Perhaps
while (!strbuf_getline(&line, f, '\n')) {
if (line.len && line.len[0] == comment_line_char)
continue;
strbuf_rtrim(&line);
if (!line.len)
continue;
abbrev_sha1_in_line(&line);
string_list_append(lines, line.buf);
}
without the "we may have added cruft, so discard them at the end"?
Other than these two minor nits, I didn't spot anything questionable
in the diff between this and the previous round.
Thanks.
next prev parent reply other threads:[~2015-07-01 16:19 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-30 13:01 [PATCH v4 0/4] More helpful 'git status' during 'rebase -i' Matthieu Moy
2015-06-30 13:01 ` [PATCH v4 1/4] status: factor two rebase-related messages together Matthieu Moy
2015-06-30 13:01 ` [PATCH v4 2/4] status: differentiate interactive from non-interactive rebases Matthieu Moy
2015-06-30 13:01 ` [PATCH v4 3/4] status: give more information during rebase -i Matthieu Moy
2015-06-30 13:01 ` [PATCH v4 4/4] status: add new tests for status " Matthieu Moy
2015-06-30 23:03 ` [PATCH v4 0/4] More helpful 'git status' during 'rebase -i' Junio C Hamano
2015-07-01 8:12 ` Matthieu Moy
2015-07-01 8:30 ` [PATCH v5 1/4] status: factor two rebase-related messages together Matthieu Moy
2015-07-01 8:30 ` [PATCH v5 2/4] status: differentiate interactive from non-interactive rebases Matthieu Moy
2015-07-01 8:30 ` [PATCH v5 3/4] status: give more information during rebase -i Matthieu Moy
2015-07-01 16:18 ` Junio C Hamano [this message]
2015-07-01 16:33 ` Eric Sunshine
2015-07-01 16:36 ` Junio C Hamano
2015-07-01 16:37 ` Eric Sunshine
2015-07-01 21:06 ` Matthieu Moy
2015-07-01 21:08 ` [PATCH v6 1/4] status: factor two rebase-related messages together Matthieu Moy
2015-07-01 21:08 ` [PATCH v6 2/4] status: differentiate interactive from non-interactive rebases Matthieu Moy
2015-07-01 21:08 ` [PATCH v6 3/4] status: give more information during rebase -i Matthieu Moy
2015-07-07 22:14 ` Junio C Hamano
2015-07-08 7:10 ` Matthieu Moy
2015-07-01 21:08 ` [PATCH v6 4/4] status: add new tests for status " Matthieu Moy
2015-07-01 21:23 ` [PATCH v5 3/4] status: give more information " Junio C Hamano
2015-07-02 8:01 ` Matthieu Moy
2015-07-03 17:40 ` Junio C Hamano
2015-07-02 8:10 ` Matthieu Moy
2015-07-01 8:30 ` [PATCH v5 4/4] status: add new tests for status " Matthieu Moy
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=xmqq4mlnc0lr.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=Matthieu.Moy@imag.fr \
--cc=antoine.delaite@ensimag.grenoble-inp.fr \
--cc=git@vger.kernel.org \
--cc=guillaume.pages@ensimag.grenoble-inp.fr \
--cc=louis--alexandre.stuber@ensimag.grenoble-inp.fr \
--cc=remi.lespinet@ensimag.grenoble-inp.fr \
/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.