From: Martin Waitz <tali@admingilde.org>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] gitweb: configurable home link string
Date: Tue, 15 Aug 2006 21:27:37 +0200 [thread overview]
Message-ID: <20060815192737.GA14459@admingilde.org> (raw)
In-Reply-To: <ebsrsn$tgq$1@sea.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 350 bytes --]
hoi :)
On Tue, Aug 15, 2006 at 06:15:05PM +0200, Jakub Narebski wrote:
> 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,
doesn't it make more sense to make it more easy to use the same URL for
git:, http: and gitweb?
--
Martin Waitz
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-08-15 19:28 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
2006-08-15 19:27 ` Martin Waitz [this message]
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=20060815192737.GA14459@admingilde.org \
--to=tali@admingilde.org \
--cc=git@vger.kernel.org \
--cc=jnareb@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).