From: cgit at cryptocrack.de (Lukas Fleischer)
Subject: [PATCH 2/2] Drop return value from parse_user()
Date: Thu, 5 Mar 2015 12:58:12 +0100 [thread overview]
Message-ID: <1425556692-1022-2-git-send-email-cgit@cryptocrack.de> (raw)
In-Reply-To: <1425556692-1022-1-git-send-email-cgit@cryptocrack.de>
In commit 936295c (Simplify commit and tag parsing, 2015-03-03), the
commit and tag parsing code was refactored. This broke tag messages in
ui-tag since the line after the tagger header was erroneously skipped.
Rework parse_user() and skip the line manually outside parse_user().
Signed-off-by: Lukas Fleischer <cgit at cryptocrack.de>
---
parsing.c | 18 +++++++-----------
1 file changed, 7 insertions(+), 11 deletions(-)
diff --git a/parsing.c b/parsing.c
index dcaf2b3..f903c7c 100644
--- a/parsing.c
+++ b/parsing.c
@@ -69,13 +69,12 @@ static char *substr(const char *head, const char *tail)
return buf;
}
-static const char *parse_user(const char *t, char **name, char **email, unsigned long *date)
+static void parse_user(const char *t, char **name, char **email, unsigned long *date)
{
- const char *line_end = strchrnul(t, '\n');
struct ident_split ident;
unsigned email_len;
- if (!split_ident_line(&ident, t, line_end - t)) {
+ if (!split_ident_line(&ident, t, strchrnul(t, '\n') - t)) {
*name = substr(ident.name_begin, ident.name_end);
email_len = ident.mail_end - ident.mail_begin;
@@ -85,11 +84,6 @@ static const char *parse_user(const char *t, char **name, char **email, unsigned
if (ident.date_begin)
*date = strtoul(ident.date_begin, NULL, 10);
}
-
- if (*line_end)
- return line_end + 1;
- else
- return line_end;
}
#ifdef NO_ICONV
@@ -152,13 +146,15 @@ struct commitinfo *cgit_parse_commit(struct commit *commit)
p += sha1hex_len + 1;
if (p && skip_prefix(p, "author ", &p)) {
- p = parse_user(p, &ret->author, &ret->author_email,
+ parse_user(p, &ret->author, &ret->author_email,
&ret->author_date);
+ p = next_header_line(p);
}
if (p && skip_prefix(p, "committer ", &p)) {
- p = parse_user(p, &ret->committer, &ret->committer_email,
+ parse_user(p, &ret->committer, &ret->committer_email,
&ret->committer_date);
+ p = next_header_line(p);
}
if (p && skip_prefix(p, "encoding ", &p)) {
@@ -211,7 +207,7 @@ struct taginfo *cgit_parse_tag(struct tag *tag)
for (p = data; !end_of_header(p); p = next_header_line(p)) {
if (skip_prefix(p, "tagger ", &p)) {
- p = parse_user(p, &ret->tagger, &ret->tagger_email,
+ parse_user(p, &ret->tagger, &ret->tagger_email,
&ret->tagger_date);
}
}
--
2.3.1
prev parent reply other threads:[~2015-03-05 11:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-05 11:58 [PATCH 1/2] Remove leading newline characters from tag messages cgit
2015-03-05 11:58 ` cgit [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=1425556692-1022-2-git-send-email-cgit@cryptocrack.de \
--to=cgit@lists.zx2c4.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).