From: Jakub Narebski <jnareb@gmail.com>
To: Gerrit Pape <pape@smarden.org>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] gitweb: fix "next" link on bottom of commit log page
Date: Mon, 02 Jun 2008 01:52:31 -0700 (PDT) [thread overview]
Message-ID: <m3d4n01anr.fsf@localhost.localdomain> (raw)
In-Reply-To: <m3y75s1a9v.fsf@localhost.localdomain>
Jakub Narebski <jnareb@gmail.com> writes:
> Gerrit Pape <pape@smarden.org> writes:
>
> > When viewing a gitweb repository commit log, the "next" link at the top
> > of the page works as expected, the "next" link on the bottom of the page
> > has a=search instead of a=log and thus fails to get you to the next
> > page. This commit replaces the bottom "next" link with the same links
> > as shown at the top of the page.
>
> > - print $cgi->a({-href => href(-replay=>1, page=>$page+1),
> > - -accesskey => "n", -title => "Alt-n"}, "next");
>
> Should not happen: href(-replay=>1, ...) should have the same value
> of 'a' parameter as the page it is in, so it should be 'log' not 'search'.
>
> Will investigate.
Now I know what is happening. git_header_html() modifies parameters
in $cgi, and href(-replay, ...) uses paramemeters values from $cgi,
not saved in variables (although it could).
So the correct solution would be to change the part which generates
search form in git_header_html() to _not_ modify $cgi->params().
Patch will follow...
P.S. I wonder if using Test::WWW::Mechanize (from CPAN) to test
gitweb's HTML output would be a good idea...
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2008-06-02 8:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-29 18:10 [PATCH] gitweb: fix "next" link on bottom of commit log page Gerrit Pape
2008-05-30 8:12 ` Jakub Narebski
2008-06-02 8:52 ` Jakub Narebski [this message]
2008-06-02 9:54 ` [PATCH] gitweb: Fix "next" link on bottom of page Jakub Narebski
2008-06-02 17:02 ` Gerrit Pape
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=m3d4n01anr.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pape@smarden.org \
/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).