From: Namhyung Kim <namhyung@kernel.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Subject: Re: [PATCH 3/3] gitweb: Add support to Link: tag
Date: Wed, 4 Jul 2012 10:24:49 +0900 [thread overview]
Message-ID: <CAM9d7ciU8j6Kt+9akyPpPiUdCJSFyL1xBbG2_c2epa79FgMmiw@mail.gmail.com> (raw)
In-Reply-To: <7vy5n0txdi.fsf@alter.siamese.dyndns.org>
Hi,
On Wed, Jul 4, 2012 at 5:15 AM, Junio C Hamano <gitster@pobox.com> wrote:
> Namhyung Kim <namhyung@kernel.org> writes:
>
>> The tip tree is the one of major subsystem tree in the
>> Linux kernel project. On the tip tree, the Link: tag is
>> used for tracking the original discussion or context.
>> Since it's ususally in the s-o-b area, it'd be better
>> using same style with others.
>>
>> Also as it tends to contain a message-id sent from git
>> send-email, a part of the line which has more than 8
>> (hex-)digit characters would set a wrong hyperlink
>> like [1]. Fix it by not using format_log_line_html().
>>
>> [1] git.kernel.org/?p=linux/kernel/git/tip/tip.git;a=commit;h=08942f6d5d992e9486b07653fd87ea8182a22fa0
>>
>> Signed-off-by: Namhyung Kim <namhyung@kernel.org>
>> ---
>> gitweb/gitweb.perl | 7 +++++++
>> 1 file changed, 7 insertions(+)
>>
>> diff --git a/gitweb/gitweb.perl b/gitweb/gitweb.perl
>> index e0701af..d07bcb7 100755
>> --- a/gitweb/gitweb.perl
>> +++ b/gitweb/gitweb.perl
>> @@ -4493,6 +4493,13 @@ sub git_print_log {
>> print "<span class=\"signoff\">" . esc_html($line) . "</span><br/>\n";
>> }
>> next;
>> + } elsif ($line =~ m,^ *link[ :](http://[\w/~.@%&=?+-]*),i) {
>
> Hrm, I am somewhat confused. This catches "link:http://..." and
> "link http://...", but not "link: http://...", which looks a lot
> more natural looking at least to me.
>
Oops, right. Actually I found it after some local testing,
but forgot to update the patch. Sorry :)
> Looking at a random sample:
>
> http://git.kernel.org/?p=linux/kernel/git/tip/tip.git;a=commit;h=fe85227347738eb9b871bc163e7fb0db8b6cd2a0
>
> I see a "Buglink: " which I think deserves to be handled by this patch
> but would not. Probably the pattern needs to be loosened
> sufficiently, e.g.
>
> m,^\s*[a-z]*link: (https?://\S+),i
>
> to catch it as well. Note that I am rejecting space before ":" and
> requiring a space after ":" in the above.
>
I think 'l' in 'link' should be '[Ll]'. Otherwise looks good to me.
> I also notice that "Reported-bisected-and-tested-by: " in that
> example, which is the topic of your [PATCH 2/3]. Perhaps the logic
> should catch everythinng that match "^[A-Z][-a-z]*[a-z]: ".
>
Isn't "^[A-Z][-A-Za-z]*-[Bb]y: " enough?
Just FYI, please see this too:
http://lwn.net/Articles/503829/
> As to coding style, if you end the body of if () clause with 'next',
> I tend to think it is easier to read if you structure it like this:
>
> if (condition 1) {
> ... action 1 ...
> next;
> }
>
> if (condition 2) {
> ... action 2 ...
> next;
> }
>
> instead of like this:
>
> if (condition 1) {
> ... action 1 ...
> next;
> } elsif (condition 2) {
> ... action 2 ...
> next;
> }
>
Ok, I'll send v2 soon after addressing all of your comments
(including previous mails).
Thanks,
Namhyung
next prev parent reply other threads:[~2012-07-04 1:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-03 6:02 [PATCH 0/3] gitweb changes Namhyung Kim
2012-07-03 6:02 ` [PATCH 1/3] gitweb: Get rid of unnecessary check of $signoff Namhyung Kim
2012-07-03 19:58 ` Junio C Hamano
2012-07-03 6:02 ` [PATCH 2/3] gitweb: Handle a few other tags in git_print_log Namhyung Kim
2012-07-03 20:05 ` Junio C Hamano
2012-07-03 6:02 ` [PATCH 3/3] gitweb: Add support to Link: tag Namhyung Kim
2012-07-03 20:15 ` Junio C Hamano
2012-07-04 1:24 ` Namhyung Kim [this message]
2012-07-04 1:30 ` Namhyung Kim
2012-07-04 1:54 ` Namhyung Kim
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=CAM9d7ciU8j6Kt+9akyPpPiUdCJSFyL1xBbG2_c2epa79FgMmiw@mail.gmail.com \
--to=namhyung@kernel.org \
--cc=acme@ghostprotocols.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).