From: Stefan Beller <sbeller@google.com>
To: "git@vger.kernel.org" <git@vger.kernel.org>,
Michael Haggerty <mhagger@alum.mit.edu>,
ronnie sahlberg <ronniesahlberg@gmail.com>,
Junio C Hamano <gitster@pobox.com>,
Jonathan Nieder <jrnieder@gmail.com>
Cc: Stefan Beller <sbeller@google.com>
Subject: Re: [PATCH] refs.c: let fprintf handle the formatting
Date: Fri, 5 Dec 2014 11:54:58 -0800 [thread overview]
Message-ID: <CAGZ79kbYDK0kJuwk+ksx3iB2cHzKvP54rCaH1o2Pknh-Axcfqw@mail.gmail.com> (raw)
In-Reply-To: <1417809221-27209-1-git-send-email-sbeller@google.com>
On Fri, Dec 5, 2014 at 11:53 AM, Stefan Beller <sbeller@google.com> wrote:
> Instead of calculating, whether to put a plus or minus sign, offload
> the responsibilty to the fprintf function.
>
> Signed-off-by: Stefan Beller <sbeller@google.com>
> ---
Ah! I forgot the --notes switch when sending out the email:
Michael,
please queue this on top of your reflog series.
More to come.
Thanks,
Stefan
> refs.c | 7 ++-----
> 1 file changed, 2 insertions(+), 5 deletions(-)
>
> diff --git a/refs.c b/refs.c
> index 40c5591..1147216 100644
> --- a/refs.c
> +++ b/refs.c
> @@ -3972,12 +3972,9 @@ static int expire_reflog_ent(unsigned char *osha1, unsigned char *nsha1,
> printf("prune %s", message);
> } else {
> if (cb->newlog) {
> - char sign = (tz < 0) ? '-' : '+';
> - int zone = (tz < 0) ? (-tz) : tz;
> - fprintf(cb->newlog, "%s %s %s %lu %c%04d\t%s",
> + fprintf(cb->newlog, "%s %s %s %lu %+05d\t%s",
> sha1_to_hex(osha1), sha1_to_hex(nsha1),
> - email, timestamp, sign, zone,
> - message);
> + email, timestamp, tz, message);
> hashcpy(cb->last_kept_sha1, nsha1);
> }
> if (cb->flags & EXPIRE_REFLOGS_VERBOSE)
> --
> 2.2.0
>
prev parent reply other threads:[~2014-12-05 19:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-05 19:53 [PATCH] refs.c: let fprintf handle the formatting Stefan Beller
2014-12-05 19:54 ` Stefan Beller [this message]
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=CAGZ79kbYDK0kJuwk+ksx3iB2cHzKvP54rCaH1o2Pknh-Axcfqw@mail.gmail.com \
--to=sbeller@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
--cc=mhagger@alum.mit.edu \
--cc=ronniesahlberg@gmail.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).