git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J.H." <warthog19@eaglescrag.net>
To: Robert Richter <robert.richter@amd.com>
Cc: git@vger.kernel.org
Subject: Re: Gitweb: Provide Git links in project list?
Date: Mon, 04 Aug 2008 09:26:54 -0700	[thread overview]
Message-ID: <1217867214.32240.61.camel@localhost.localdomain> (raw)
In-Reply-To: <20080804101200.GC811@erda.amd.com>

Robert,

Noticed, but while I agree cloneurl is good - I think it kind of defeats
the purpose of what I was originally intending with the 'git' link.
I've gone back in to understand cloneurl better and I genuinely think
this is the wrong approach (or at least not what was originally intended
with the 'git' link as I envisioned it).

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. 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.

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

(2) ignoring my comments on why I think using cloneurl for a large site
is bad (after I looked into it), blindly on taking the first option in
the file may lead to the display of unexpected or unintended URLs.

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.

- John 'Warthog9' Hawley

On Mon, 2008-08-04 at 12:12 +0200, Robert Richter wrote:
> On 03.08.08 13:53:13, J.H. wrote:
> > Working on refactoring the patch so that it can go upstream, one of the
> > things I'm definitely making an assumption about (in my original code)
> > is that the base url will be uniform for the entire project_list (as it
> > is on kernel.org).  If that's acceptable I will probably be able to
> > submit something today, if not I will need to muck about and read out
> > the url from .git/cloneurl (which would be a rather hefty performance
> > hit - needing to read that from each repository)
> 
> John,
> 
> I just sent out a patch that implements this using cloneurl. It seemed
> small and easy to implement and so I just made the change myself.
> 
> Thank you anyway.
> 
> -Robert
> 

  reply	other threads:[~2008-08-04 16:28 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. [this message]
2008-08-04 20:10           ` Petr Baudis
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=1217867214.32240.61.camel@localhost.localdomain \
    --to=warthog19@eaglescrag.net \
    --cc=git@vger.kernel.org \
    --cc=robert.richter@amd.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).