From: cgit at cryptocrack.de (Lukas Fleischer)
Subject: [PATCH 1/2] Remove leading newline characters from tag messages
Date: Thu, 5 Mar 2015 12:58:11 +0100 [thread overview]
Message-ID: <1425556692-1022-1-git-send-email-cgit@cryptocrack.de> (raw)
Fixes a regression introduced in commit 936295c (Simplify commit and tag
parsing, 2015-03-03).
Signed-off-by: Lukas Fleischer <cgit at cryptocrack.de>
---
parsing.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/parsing.c b/parsing.c
index 0db181b..dcaf2b3 100644
--- a/parsing.c
+++ b/parsing.c
@@ -216,6 +216,9 @@ struct taginfo *cgit_parse_tag(struct tag *tag)
}
}
+ while (p && *p == '\n')
+ p++;
+
if (p && *p)
ret->msg = xstrdup(p);
--
2.3.1
next 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 cgit [this message]
2015-03-05 11:58 ` [PATCH 2/2] Drop return value from parse_user() cgit
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-1-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).