From: Petr Baudis <pasky@suse.cz>
To: "J.H." <warthog19@eaglescrag.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 1/1] Add "git" link to the end of project line on the project_list page.
Date: Mon, 4 Aug 2008 05:20:44 +0200 [thread overview]
Message-ID: <20080804032044.GG10151@machine.or.cz> (raw)
In-Reply-To: <1217817517.32240.46.camel@localhost.localdomain>
On Sun, Aug 03, 2008 at 07:38:37PM -0700, J.H. wrote:
> On Mon, 2008-08-04 at 04:26 +0200, Petr Baudis wrote:
> > On Sun, Aug 03, 2008 at 07:00:17PM -0700, warthog19@eaglescrag.net wrote:
> > > diff --git a/gitweb/gitweb.perl b/gitweb/gitweb.perl
> > > index 90cd99b..c33f4ed 100755
> > > --- a/gitweb/gitweb.perl
> > > +++ b/gitweb/gitweb.perl
> > > @@ -108,6 +108,14 @@ our $mimetypes_file = undef;
> > > # could be even 'utf-8' for the old behavior)
> > > our $fallback_encoding = 'latin1';
> > >
> > > +# enable / disable a final link on the project list page
> > > +# that will be the location of that actuall git url
> > > +# it will output this in the format:
> > > +# git://hostname/path/to/tree.git
> > > +# disabled = blank or undef
> > > +# enable = url to prefix before filling in the trailing path to the git repo
> > > +our $projectlist_gitlinkurl = undef;
> > > +
> > > # rename detection options for git-diff and git-diff-tree
> > > # - default is '-M', with the cost proportional to
> > > # (number of removed files) * (number of new files).
By the way, you should add this to gitweb/README too (though I've never
been too fond of listing the options twice myself; my strategy to avoid
it is to just add as much stuff possible to the $features hash ;-).
> > > + if( $projectlist_gitlinkurl != undef && $projectlist_gitlinkurl ne "" ){
Coding style conformant and equivalent but simpler variant would be
if ($projectlist_gitlinkurl) {
right?
> > > + print " | ". $cgi->a({-href => "git://projectlist_gitlinkurl/".esc_html($pr->{'path'})}, "git");
> >
> > You meant $projectlist_gitlinkurl.
>
> grrr - I've fixed that same bug twice now, had problems with something
> and must have reverted the wrong thing, I'll fix it and re-submit.
>
> When you do the more generic patch to extend the links I'll flip this
> over to that code, unless you think it's worth holding off and waiting
> for that change to go in first?
It's a new feature so it probably won't make it to 1.6.0 - so let's see
if I manage to submit mine before 1.6.0. ;-)
--
Petr "Pasky" Baudis
The next generation of interesting software will be done
on the Macintosh, not the IBM PC. -- Bill Gates
prev parent reply other threads:[~2008-08-04 3:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-04 2:00 [PATCH 0/1] : [GITWEB] : Git link on project list page warthog19
2008-08-04 2:00 ` [PATCH 1/1] Add "git" link to the end of project line on the project_list page warthog19
2008-08-04 2:26 ` Petr Baudis
2008-08-04 2:38 ` J.H.
2008-08-04 3:20 ` Petr Baudis [this message]
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=20080804032044.GG10151@machine.or.cz \
--to=pasky@suse.cz \
--cc=git@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.