From: Junio C Hamano <junkio@cox.net>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 2/2] gitweb: Add support for per project git URLs
Date: Wed, 16 Aug 2006 13:40:33 -0700 [thread overview]
Message-ID: <7vveos2z3y.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <200608161450.35118.jnareb@gmail.com> (Jakub Narebski's message of "Wed, 16 Aug 2006 14:50:34 +0200")
Jakub Narebski <jnareb@gmail.com> writes:
> It is now possible for project to have individual clone/fetch URLs.
> They are provided in new file 'cloneurl' added below project's
> $GIT_DIR directory.
>
> If there is no cloneurl file, concatenation of git base URLs with
> project name is used.
>
> This is merge of Jakub Narebski and David Rientjes
> gitweb: Show project's git URL on summary page
> with Aneesh Kumar
> gitweb: Add support for cloneurl.
> gitweb: Support multiple clone urls
> patches.
>
> Signed-off-by: Jakub Narebski <jnareb@gmail.com>
> Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@gmail.com>
I'll take this for now, but we might want to consider moving
'description' and 'cloneurl' information to the config file to
prevent cluttering.
gitweb.description
gitweb.giturl
The URL is not for cloning only, but also for fetch/pull, right?
next prev parent reply other threads:[~2006-08-16 20:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-15 18:03 [PATCH] gitweb: Show project's git URL on summary page Jakub Narebski
2006-08-15 18:43 ` David Rientjes
2006-08-15 19:32 ` Jakub Narebski
2006-08-15 21:03 ` [PATCH (revised)] " Jakub Narebski
2006-08-15 21:36 ` David Rientjes
2006-08-16 7:31 ` Aneesh Kumar K.V
2006-08-16 12:56 ` Jakub Narebski
2006-08-16 12:50 ` [PATCH 2/2] gitweb: Add support for per project git URLs Jakub Narebski
2006-08-16 20:40 ` Junio C Hamano [this message]
2006-08-17 9:31 ` Jakub Narebski
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=7vveos2z3y.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--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).