From: Petr Baudis <pasky@suse.cz>
To: "J.H." <warthog19@eaglescrag.net>
Cc: Robert Richter <robert.richter@amd.com>, git@vger.kernel.org
Subject: Re: Gitweb: Provide Git links in project list?
Date: Mon, 4 Aug 2008 22:10:20 +0200 [thread overview]
Message-ID: <20080804201020.GB32184@machine.or.cz> (raw)
In-Reply-To: <1217867214.32240.61.camel@localhost.localdomain>
Hi,
On Mon, Aug 04, 2008 at 09:26:54AM -0700, J.H. wrote:
> The git link was always meant / intended to be a link to acquire the git
> repository directly, and be independent of what is actually present in
> the cloneurl file, specifically I wanted it to be a (1) git url
> (git://<hostname>/<path>) so that it took advantage of git specifically
> vs. accidentally giving you something with ssh or http.
we could grep the cloneurl.
The thing is, some sites like repo.or.cz don't use per-project
cloneurl but do specify pull URLs by @git_base_url_list and this is
introducing unnecessary redundancy.
> and (2) was
> uniform and did *not* depend on something in the repository as with
> large set of repositories, kernel.org, there is no way we can police
> this and we explicitly do not want to have a script that automatically
> adds this or what not.
Then why do you allow cloneurl in the repositories at all, if you
think the links won't be trustworthy? What is the fundamental difference
between what you show on the project list page and the URLs in the
project summary page?
> I have two other concerns with the patch your proposing
>
> (1) it's on by default, and it seems that there are a number of sites
> that don't actually want this functionality, making it a configurable
> option would seem prudent in that case
I actually plan to remove the 'log' link from the project list; I
really wonder about the practicality of the 'git' link... but if there
were any widely used browser integrations (like firing up git-gui when
clicking on a git:// link), I *would* definitely see it more useful than
the 'log' link and add it to repo.or.cz. But I have never heard about
anyone actually doing this (but I think it might make a lot of sense;
thinking about it, I might try to patch msysgit to do this on Windows,
this would be nifty for my current dayjob project :).
> That said, it's probably worth merging the two patches (since I'm
> already there with the configuration options, etc) that way people can
> get either functionality should they choose.
Configuration options are expensive on human users. Please let's not
add more too carelessly.
--
Petr "Pasky" Baudis
The next generation of interesting software will be done
on the Macintosh, not the IBM PC. -- Bill Gates
next prev parent reply other threads:[~2008-08-04 20:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-30 12:57 Gitweb: Provide Git links in project list? Robert Richter
2008-07-30 13:02 ` Fredrik Skolmli
2008-07-30 13:13 ` Robert Richter
2008-07-30 13:29 ` Fredrik Skolmli
2008-07-30 14:55 ` Bert Wesarg
2008-07-30 15:27 ` Robert Richter
2008-07-30 15:49 ` J.H.
2008-07-30 16:11 ` Robert Richter
2008-08-03 20:53 ` J.H.
2008-08-04 10:06 ` [PATCH] Gitweb: Provide Git links in project list Robert Richter
2008-08-04 10:12 ` Gitweb: Provide Git links in project list? Robert Richter
2008-08-04 16:26 ` J.H.
2008-08-04 20:10 ` Petr Baudis [this message]
2008-07-30 16:41 ` Boyd Lynn Gerber
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=20080804201020.GB32184@machine.or.cz \
--to=pasky@suse.cz \
--cc=git@vger.kernel.org \
--cc=robert.richter@amd.com \
--cc=warthog19@eaglescrag.net \
/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).