From: Petr Baudis <pasky@suse.cz>
To: Jakub Narebski <jnareb@gmail.com>
Cc: Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com>, git@vger.kernel.org
Subject: Re: Possible but in gitweb
Date: Sat, 18 Nov 2006 19:41:42 +0100 [thread overview]
Message-ID: <20061118184142.GN7201@pasky.or.cz> (raw)
In-Reply-To: <200611181901.31708.jnareb@gmail.com>
On Sat, Nov 18, 2006 at 07:01:30PM CET, Jakub Narebski wrote:
> Paolo Ciarrocchi wrote:
> > On 11/18/06, Jakub Narebski <jnareb@gmail.com> wrote:
> >> Paolo Ciarrocchi wrote:
> >>>
> >>> Browsing the repo I reach the following URL
> >>> http://repo.or.cz/w/LinuxKernelDevelopmentProcess.git?a=blob;f=LinuxKernelDevelopmentProcess.html;hb=HEAD
> >>> that is not accessible.
> >>
> >> Because HEAD is master, not html, and there us no such file in master branch?
> >
> > Fair enough but then there should be no link in the web interface.
> > That sounds like a bug in the interface.
>
> Where did you find this link? On what page?
>
> "Browsing the repo" is not enough information to discover where
> there is a bug.
It's not really hard to find. :-)
http://repo.or.cz/w/LinuxKernelDevelopmentProcess.git?a=blob;f=LinuxKernelDevelopmentProcess.html;h=b5e39498997930cd14ecddfe120f62c577ce2e28;hb=html
I think the link shouldn't be 'HEAD' but 'latest' and point to the
latest version in the currently browser branch.
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
The meaning of Stonehenge in Traflamadorian, when viewed from above, is:
"Replacement part being rushed with all possible speed."
prev parent reply other threads:[~2006-11-18 18:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-18 16:58 Possible but in gitweb Paolo Ciarrocchi
2006-11-18 17:35 ` Jakub Narebski
2006-11-18 17:42 ` Paolo Ciarrocchi
2006-11-18 18:01 ` Jakub Narebski
[not found] ` <4d8e3fd30611181003o6374f01cy504c0c058f374f1@mail.gmail.com>
2006-11-18 18:21 ` Jakub Narebski
2006-11-18 19:06 ` Luben Tuikov
2006-11-18 18:41 ` Petr Baudis [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=20061118184142.GN7201@pasky.or.cz \
--to=pasky@suse.cz \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=paolo.ciarrocchi@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).