From: Junio C Hamano <gitster@pobox.com>
To: Thomas Perl <th.perl@gmail.com>
Cc: Jakub Narebski <jnareb@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH 1/2] gitweb: Fix file links in "grep" search
Date: Fri, 13 Jan 2012 11:18:42 -0800 [thread overview]
Message-ID: <7v62gfza0d.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <CA+uOhx7QwRQJzyYBCkmVDBRCMt0i_ZqS=sfTG0VmNiVv2dVoww@mail.gmail.com> (Thomas Perl's message of "Fri, 13 Jan 2012 15:09:27 +0100")
Thomas Perl <th.perl@gmail.com> writes:
> As far as I'm concerned, the patch can be applied and fixes the bug.
Thanks.
prev parent reply other threads:[~2012-01-13 19:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-02 13:29 [BUG] gitweb generates wrong links in grep search results (git_search_files) Thomas Perl
2012-01-04 0:28 ` Junio C Hamano
2012-01-04 16:21 ` Jakub Narębski
2012-01-05 20:26 ` [PATCH 1/2] gitweb: Fix file links in "grep" search Jakub Narebski
2012-01-05 20:32 ` [PATCH 2/2] gitweb: Harden "grep" search against filenames with ':' Jakub Narebski
2012-01-13 14:09 ` [PATCH 1/2] gitweb: Fix file links in "grep" search Thomas Perl
2012-01-13 19:18 ` Junio C Hamano [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=7v62gfza0d.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=th.perl@gmail.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).