git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: Wincent Colaiuta <win@wincent.com>
Cc: Git Mailing List <git@vger.kernel.org>, Petr Baudis <pasky@suse.cz>
Subject: Re: gitweb bug: broken "next" and other links
Date: Mon, 11 Feb 2008 05:02:31 -0800 (PST)	[thread overview]
Message-ID: <m3ve4vejdr.fsf@localhost.localdomain> (raw)
In-Reply-To: <B0EC9FB3-DDDE-4BC5-92D8-20487CBD6725@wincent.com>

Wincent Colaiuta <win@wincent.com> writes:

> Just noticed a bug (possibly bugs) in gitweb.
> 
> Look at a shortlog page like this one:
> 
>   http://repo.or.cz/w/git.git?a=shortlog
> 
> Mouse over the "next" link at the bottom and you'll see this is the URL:
> 
>   http://repo.or.cz/w/ARRAY(0x85a5318)?a=shortlog;pg=1
> 
> Which obviously won't work...

This is bug in repo.or.cz version of gitweb, which is slightly
modified as compared to the "stock" version. Such error would be
catched by the gitweb 'run as standalone script and check stderr'
test script.

I have CC-ed Pasky.
-- 
Jakub Narebski
Poland
ShadeHawk on #git

  reply	other threads:[~2008-02-11 13:03 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 [this message]
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
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=m3ve4vejdr.fsf@localhost.localdomain \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.org \
    --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 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).