From: mail at eworm.de (Christian Hesse)
Subject: [PATCH 1/1] enable cgit to show gravatar for author, committer and tagger
Date: Thu, 9 Jan 2014 10:13:55 +0100 [thread overview]
Message-ID: <20140109101355.0ddca426@leda.localdomain> (raw)
In-Reply-To: <CAHmME9rjttQv3y0=W8iTM1ArY9o=tNAFyNOBh8EV2y=KuXWbig@mail.gmail.com>
"Jason A. Donenfeld" <Jason at zx2c4.com> on Wed, 2014/01/08 17:00:
> Sorry for the extended nitpicks....
>
> On Wed, Jan 8, 2014 at 4:23 PM, Christian Hesse <mail at eworm.de> wrote:
> > +char *cgit_get_gravatar(const char *email)
> > +{
> > +
> > + /* duplicate to lower and skip brackets! */
> > + lower = strdup(email + 1);
> > + lower[strlen(lower) - 1] = '\0';
>
> Can email ever be passed in with no length at all? Or without
> brackets? It's not immediately clear to me from looking briefly at
> parse_user in parsing.c.
A really good question. Let's think about parse_user()... If t does not
include brackets the string ends up in name. If it does include brackets the
address ends up in email, including the brackets. So does (mode == 2 && *p ==
'\n') ever get true? Probably we have a piece of dead code.
I think email always includes brackets or is NULL. In later case
cgit_get_gravatar() is not executed, so everything should be fine.
--
Schoene Gruesse
Chris
O< ascii ribbon campaign
stop html mail - www.asciiribbon.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://lists.zx2c4.com/pipermail/cgit/attachments/20140109/8fbd411d/attachment.asc>
next prev parent reply other threads:[~2014-01-09 9:13 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-08 14:34 Welcome on board Lukas Fleischer Jason
2014-01-08 14:53 ` [RESEND PATCH 1/1] enable cgit to show gravatar for author, committer and tagger mail
2014-01-08 15:12 ` Jason
2014-01-08 15:23 ` [PATCH " mail
2014-01-08 15:56 ` Jason
2014-01-09 8:52 ` mail
2014-01-09 15:13 ` Jason
2014-01-08 16:00 ` Jason
2014-01-09 9:13 ` mail [this message]
2014-01-08 15:36 ` [RESEND PATCH " mathstuf
2014-01-08 17:15 ` normalperson
2014-01-08 17:29 ` Jason
2014-01-08 18:35 ` stefan
2014-01-09 9:18 ` list
2014-01-09 15:19 ` Jason
2014-01-13 14:18 ` list
2014-01-13 14:24 ` Jason
2014-01-14 17:22 ` list
2014-01-14 17:23 ` Jason
2014-01-14 17:35 ` list
2014-01-14 17:45 `
2014-01-14 17:51 ` Jason
2014-01-14 17:58 ` list
2014-01-14 18:00 ` Jason
2014-01-09 15:21 ` RFE: author/committer/tagger links (enable cgit to show gravatar for author, committer and tagger) mricon
2014-01-09 17:50 ` Jason
2014-01-09 18:07 ` john
2014-01-09 18:59 ` Jason
2014-01-09 19:23 ` john
2014-01-09 19:34 ` cgit
2014-01-09 19:38 ` Welcome on board Lukas Fleischer info
-- strict thread matches above, loose matches on Subject: below --
2013-11-27 15:17 [PATCH 1/1] enable cgit to show gravatar for author, committer and tagger mail
2013-11-27 16:17 ` list
2013-11-27 16:37 ` john
2013-11-27 20:51 ` list
2013-11-27 21:00 ` john
2013-11-27 16:46 ` lekensteyn
2013-11-27 20:59 ` list
2013-11-27 21:14 ` mail
2013-11-27 22:11 ` lekensteyn
2013-11-27 22:59 ` list
2013-11-27 23:00 ` mail
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=20140109101355.0ddca426@leda.localdomain \
--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).