From: "René Scharfe" <l.s.r@web.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: [PATCH 2/2] use strbuf_add_unique_abbrev() for adding short hashes, part 2
Date: Tue, 27 Sep 2016 22:59:03 +0200 [thread overview]
Message-ID: <3c80f7d7-a145-3a4a-4bf2-2d8fb6dda04b@web.de> (raw)
In-Reply-To: <xmqqshslm6jo.fsf@gitster.mtv.corp.google.com>
Am 27.09.2016 um 22:28 schrieb Junio C Hamano:
> René Scharfe <l.s.r@web.de> writes:
>> diff --git a/submodule.c b/submodule.c
>> index dcc5ce3..8cf40ea 100644
>> --- a/submodule.c
>> +++ b/submodule.c
>> @@ -396,7 +396,7 @@ static void show_submodule_header(FILE *f, const char *path,
>> find_unique_abbrev(one->hash, DEFAULT_ABBREV));
>> if (!fast_backward && !fast_forward)
>> strbuf_addch(&sb, '.');
>> - strbuf_addstr(&sb, find_unique_abbrev(two->hash, DEFAULT_ABBREV));
>> + strbuf_add_unique_abbrev(&sb->hash, two, DEFAULT_ABBREV);
>
> I wonder how could this change come out of this definition:
>
> @@
> expression E1, E2, E3;
> @@
> - strbuf_addstr(E1, find_unique_abbrev(E2, E3));
> + strbuf_add_unique_abbrev(E1, E2, E3);
Impossible. I added "->hash" manually during a rebase (merging
a0d12c44, wrongly). Good catch, thanks!
Seeing proof of skipping compile-testing I wonder what else I do
forget in my daily life. :-| I'll better go to sleep now..
Fixup patch, generated by reverting the diff, re-adding the
semantic patch and using coccicheck; compiles and survives make
test:
---
submodule.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/submodule.c b/submodule.c
index 8cf40ea..bb06b60 100644
--- a/submodule.c
+++ b/submodule.c
@@ -396,7 +396,7 @@ static void show_submodule_header(FILE *f, const char *path,
find_unique_abbrev(one->hash, DEFAULT_ABBREV));
if (!fast_backward && !fast_forward)
strbuf_addch(&sb, '.');
- strbuf_add_unique_abbrev(&sb->hash, two, DEFAULT_ABBREV);
+ strbuf_add_unique_abbrev(&sb, two->hash, DEFAULT_ABBREV);
if (message)
strbuf_addf(&sb, " %s%s\n", message, reset);
else
--
2.10.0
next prev parent reply other threads:[~2016-09-27 20:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-27 19:08 [PATCH 1/2] use strbuf_addstr() instead of strbuf_addf() with "%s", part 2 René Scharfe
2016-09-27 19:11 ` [PATCH 2/2] use strbuf_add_unique_abbrev() for adding short hashes, " René Scharfe
2016-09-27 20:28 ` Junio C Hamano
2016-09-27 20:59 ` René Scharfe [this message]
2016-10-07 0:46 ` Jeff King
2016-10-07 20:45 ` René Scharfe
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=3c80f7d7-a145-3a4a-4bf2-2d8fb6dda04b@web.de \
--to=l.s.r@web.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).