From: "Marco Costalba" <mcostalba@gmail.com>
To: "Junio C Hamano" <gitster@pobox.com>
Cc: "Git Mailing List" <git@vger.kernel.org>,
"René Scharfe" <rene.scharfe@lsrfire.ath.cx>
Subject: Re: [PATCH] Fix an off by one bug in pretty.c
Date: Sun, 6 Jan 2008 00:18:37 +0100 [thread overview]
Message-ID: <e5bfff550801051518u49e9c21ake36584457f4c9488@mail.gmail.com> (raw)
In-Reply-To: <e5bfff550801051455i3d589c4q9375aeab0cb6aa47@mail.gmail.com>
On Jan 5, 2008 11:55 PM, Marco Costalba <mcostalba@gmail.com> wrote:
> In case author email is <> then we have the following
> bug in function 'format_person_part'
>
WARNING: Please discard previous patch!
Due to an error I sent the wrong one, the following is the correct one:
------------------- CUT ----------------------------------------------------
In case author email is <> then we have the following
bug in function 'format_person_part'
/* parse name */
for (end = 0; end < len && msg[end] != '<'; end++)
; /* do nothing */
start = end + 1; /* now start points to '>' */
-- cut ---
/* parse email */
for (end = start + 1; end < len && msg[end] != '>'; end++)
And here 'end' is initialized with 'start + 1'
instead of 'start'. This turns out in empty commit
date when git log is used with --pretty=format option.
Signed-off-by: Marco Costalba <mcostalba@gmail.com>
---
feba083ccd11374560e34a755ca03f07e7d45533
pretty.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/pretty.c b/pretty.c
index 5b1078b..3ce5e6f 100644
--- a/pretty.c
+++ b/pretty.c
@@ -304,7 +304,7 @@ static void format_person_part
return;
/* parse email */
- for (end = start + 1; end < len && msg[end] != '>'; end++)
+ for (end = start; end < len && msg[end] != '>'; end++)
; /* do nothing */
if (end >= len)
prev parent reply other threads:[~2008-01-05 23:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-05 22:55 [PATCH] Fix an off by one bug in pretty.c Marco Costalba
2008-01-05 23:18 ` Marco Costalba [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=e5bfff550801051518u49e9c21ake36584457f4c9488@mail.gmail.com \
--to=mcostalba@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=rene.scharfe@lsrfire.ath.cx \
/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).