From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH] gitweb: configurable home link string
Date: Tue, 15 Aug 2006 18:15:05 +0200 [thread overview]
Message-ID: <ebsrsn$tgq$1@sea.gmane.org> (raw)
In-Reply-To: 11555958491891-git-send-email-yashi@atmark-techno.com
Yasushi SHOJI wrote:
> I've always found difficult to figure out git URL for clone from
> gitweb URL because git:// and http:// are different on many site
> including kernel.org.
>
> I've found this enhancement at http://dev.laptop.org/git when I was on
> git channel, and thought that it'd be nice if all public gitweb site
> show it's git URL on its page.
>
> This patch allow us to change the home link string. The current
> default is "projects" as we all see on gitweb now.
>
> ie. kernel.org might set this variable to "git://git.kernel.org/pub/scm/"
>
> Signed-off-by: Yasushi SHOJI <yashi@atmark-techno.com>
There is similar improvement in gitweb-xmms2, where the git clone/fetch
URL for an individual project is visible in the "summary" page for project,
see e.g.
http://git.xmms.se/?p=gitweb-xmms2.git;a=summary
I plan on implementing such a feature, with an improvement that URL is not
displayed if $git_base_url (your $home_link_str) is not defined (e.g.
repository is not published)... or you can reimplement this feature.
http://git.xmms.se/?p=gitweb-xmms2.git;a=commit;h=8e327dfbdebedd0c5fc02fe606fd4675b43237d7
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2006-08-15 16:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-14 22:50 [PATCH] gitweb: configurable home link string Yasushi SHOJI
2006-08-15 16:15 ` Jakub Narebski [this message]
2006-08-15 19:27 ` Martin Waitz
2006-08-15 19:36 ` Jakub Narebski
2006-08-15 20:24 ` Carl Worth
2006-08-15 22:11 ` Martin Waitz
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='ebsrsn$tgq$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.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).