From: john at keeping.me.uk (John Keeping)
Subject: [PATCH 2/3] Remove angle brackets from {author,committer}_email
Date: Fri, 24 Feb 2017 11:19:10 -0500 [thread overview]
Message-ID: <8d32e1cd-e517-6d50-4754-2d5929cb9f24@bnl.gov> (raw)
In-Reply-To: <cover.1487952449.git.smithj4@bnl.gov>
This matches the internal representation in libgit.a, so it will make it
much easier to use Git's mailmap code.
The change in ui-atom.c isn't strictly necessary since the code copes
with email addresses both with and without angle brackets, but it's a
nice simplification since we know that the email address will always be
provided in the correct form.
Signed-off-by: John Keeping <john at keeping.me.uk>
Signed-off-by: Jason A. Smith <smithj4 at bnl.gov>
---
filter.c | 10 +++++++++-
parsing.c | 6 +-----
ui-atom.c | 13 +------------
ui-commit.c | 6 ++++--
ui-tag.c | 3 ++-
5 files changed, 17 insertions(+), 21 deletions(-)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0002-Remove-angle-brackets-from-author-committer-_email.patch
Type: text/x-patch
Size: 3385 bytes
Desc: not available
URL: <http://lists.zx2c4.com/pipermail/cgit/attachments/20170224/9913690b/attachment.bin>
next prev parent reply other threads:[~2017-02-24 16:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1487952449.git.smithj4@bnl.gov>
2017-02-24 16:18 ` [PATCH 1/3] filter: introduce cgit_open_email_filter() wrapper john
2017-02-25 9:01 ` Jason
2017-02-24 16:19 ` john [this message]
2017-02-24 16:19 ` [PATCH 3/3] Add support for git's mailmap smithj4
2017-02-25 16:12 [PATCH 0/3] " smithj4
2017-02-25 16:12 ` [PATCH 2/3] Remove angle brackets from {author,committer}_email smithj4
[not found] <b710a9bcd7a1408c429ec09f535916074b957d25.1472494937.git.smithj4@bnl.gov>
2016-08-29 18:28 ` john
-- strict thread matches above, loose matches on Subject: below --
2016-08-26 20:12 john
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=8d32e1cd-e517-6d50-4754-2d5929cb9f24@bnl.gov \
--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).