From: Jakub Narebski <jnareb@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Wincent Colaiuta <win@wincent.com>,
Git Mailing List <git@vger.kernel.org>,
Petr Baudis <pasky@suse.cz>
Subject: Re: gitweb bug: broken "next" and other links
Date: Tue, 19 Feb 2008 01:23:13 +0100 [thread overview]
Message-ID: <200802190123.14112.jnareb@gmail.com> (raw)
In-Reply-To: <7v8x1hom3n.fsf@gitster.siamese.dyndns.org>
Junio C Hamano wrote:
> Jakub Narebski <jnareb@gmail.com> writes:
>
> > Junio, would you consider applying one of those patches? Any of them
> > should fix the bug; the second one is less intrusive.
>
> Surely.
>
> By "the second one" do you mean this one?
>
> Subject: [PATCH] gitweb: Add new option -nohtml to quot_xxx subroutines
> Date: Sun, 17 Feb 2008 18:48:13 +0100
> Message-ID: <20080217174812.30454.86822.stgit@localhost.localdomain>
The above is purely meant to further enhance 850b90a51d5
gitweb: Fix displaying unchopped argument in chop_and_escape_str
No, I meant:
Subject: [PATCH] gitweb: Fix bug in href(..., -replay=>1) when 'pathinfo' feature used
Date: Thu, 14 Feb 2008 09:22:30 +0100
Message-Id: <200802152216.42533.jnareb@gmail.com>
It is inside other email (Re: gitweb bug: broken "next" and other links),
so I can resend it...
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2008-02-19 0:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-11 12:51 gitweb bug: broken "next" and other links Wincent Colaiuta
2008-02-11 13:02 ` Jakub Narebski
2008-02-11 13:33 ` Wincent Colaiuta
2008-02-11 15:30 ` Jakub Narebski
2008-02-12 11:39 ` Jakub Narebski
2008-02-12 11:48 ` Jakub Narebski
2008-02-12 12:24 ` Wincent Colaiuta
2008-02-12 13:10 ` Jakub Narebski
2008-02-12 13:34 ` Wincent Colaiuta
2008-02-15 21:16 ` Jakub Narebski
2008-02-17 10:51 ` Wincent Colaiuta
2008-02-17 11:05 ` Junio C Hamano
2008-02-18 23:32 ` Jakub Narebski
2008-02-18 23:56 ` Junio C Hamano
2008-02-19 0:23 ` Jakub Narebski [this message]
2008-02-19 0:23 ` Wincent Colaiuta
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=200802190123.14112.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pasky@suse.cz \
--cc=win@wincent.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.