From: He Sun <sunheehnus@gmail.com>
To: Eric Sunshine <sunshine@sunshineco.com>, git <git@vger.kernel.org>
Subject: Re: [PATCH v3] write_pack_file: use correct variable in diagnostic
Date: Mon, 3 Mar 2014 09:20:21 +0800 [thread overview]
Message-ID: <CAJr59C1Azr9EnoeRPKZF+AB9GBw1RR7fUkvaYChyTfHwoJSvFA@mail.gmail.com> (raw)
In-Reply-To: <CAPig+cSuBfuzL-NXYkvFoz5+jPrEUNfTqoMf-iAYyMSv3jDsqg@mail.gmail.com>
2014-03-03 2:42 GMT+08:00 Eric Sunshine <sunshine@sunshineco.com>:
> On Sun, Mar 2, 2014 at 2:30 AM, Sun He <sunheehnus@gmail.com> wrote:
>> 'pack_tmp_name' is the subject of the utime() check, so report it in the
>> warning, not the uninitialized 'tmpname'
>>
>> Signed-off-by: Sun He <sunheehnus@gmail.com>
>> ---
>>
>> Changing the subject and adding valid information as tutored by
>> Eric Sunshine.
>> Thanks to him.
>>
>> builtin/pack-objects.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/builtin/pack-objects.c b/builtin/pack-objects.c
>> index c733379..4922ce5 100644
>> --- a/builtin/pack-objects.c
>> +++ b/builtin/pack-objects.c
>> @@ -823,7 +823,7 @@ static void write_pack_file(void)
>> utb.modtime = --last_mtime;
>> if (utime(pack_tmp_name, &utb) < 0)
>> warning("failed utime() on %s: %s",
>> - tmpname, strerror(errno));
>> + pack_tmp_name, strerror(errno));
>> }
>>
>> /* Enough space for "-<sha-1>.pack"? */
>> --
>> 1.9.0.138.g2de3478.dirty
>
> Nicely done. Everything is where it ought to be.
>
> As this is an actual bug fix (not just a GSoC microproject):
>
> Reviewed-by: Eric Sunshine <sunshine@sunshineco.com>
Thank you so much for everything you have done.
I am honored to do this with all your support and kindness.
Regards,
He Sun
next prev parent reply other threads:[~2014-03-03 1:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-02 7:30 [PATCH v3] write_pack_file: use correct variable in diagnostic Sun He
2014-03-02 18:42 ` Eric Sunshine
2014-03-03 1:20 ` He Sun [this message]
2014-03-03 18:43 ` Junio C Hamano
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=CAJr59C1Azr9EnoeRPKZF+AB9GBw1RR7fUkvaYChyTfHwoJSvFA@mail.gmail.com \
--to=sunheehnus@gmail.com \
--cc=git@vger.kernel.org \
--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 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).