git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jochen Roemling <jochen@roemling.net>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: Git Mailing List <git@vger.kernel.org>,
	Sebastian Kuzminsky <seb@highlab.com>
Subject: Re: change of git-diff-tree and symlinks
Date: Sun, 29 May 2005 18:06:38 +0200	[thread overview]
Message-ID: <4299E88E.7090306@roemling.net> (raw)
In-Reply-To: <20050529150656.GA27127@vrfy.org>

[resending in plain-text]

Kay Sievers wrote:

>The kernel.org servers use Cogito which needs a new release. So the
>version on kernel.org is always a working version with the current
>release of Cogito as long as we don't get a git-core to provide the
>binaries.
>  
>
Ah yes, I remember the discussion about that.
Sebastian, could you include a matching gitweb.cgi into your 
Debian-Package?

And what about something like:

if (-e '/etc/gitweb.conf') { requite '/etc/gitweb.conf'; }

after the variable settings? The included file would then set 
$projectroot and friends to the local values so that I don't have to 
patch gitweb everytime I upgrade it. Since perl has no plain "include" 
and the require doesn't really work for me (it seems to include the 
file, but the variables stay the same), I leave it up to you (I would 
have been so proud to provide you a patch, but obviously my perl 
knowledge is worse than I thought).

>My latest version is here:
>  ftp://ehlo.org/gitweb.cgi
>  
>
Thanks for pointing that out. I had the impression, on ehlo.org is only 
a installed version, not a downloadable one.

>>And as a last side note it would be helpfull if you could include a 
>>release number in the gitweb footer as you did in the very beginning so 
>>that we know if something changed and there is new stuff to explore...
>>    
>>
>
>It is in the html-source, right at the top.
>  
>
Good hiding-place....

Jochen

  reply	other threads:[~2005-05-29 16:04 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-25 11:17 change of git-diff-tree and symlinks Kay Sievers
2005-05-25 18:08 ` Linus Torvalds
2005-05-25 18:35   ` Kay Sievers
2005-05-25 19:40     ` Junio C Hamano
2005-05-25 22:06       ` [PATCH] Adjust show-files test for dotfiles Junio C Hamano
2005-05-25 22:07       ` [PATCH] Fix type-change handling when assigning the status code to filepairs Junio C Hamano
2005-05-25 22:26       ` change of git-diff-tree and symlinks Kay Sievers
2005-05-25 22:43         ` Junio C Hamano
2005-05-25 22:47         ` Linus Torvalds
2005-05-25 23:00           ` [PATCH] Mode only changes from diff Junio C Hamano
2005-05-26  2:11             ` [PATCH] Test case portability fix Junio C Hamano
2005-05-26  2:36               ` Linus Torvalds
2005-05-26  2:55                 ` Junio C Hamano
2005-05-29 14:16 ` change of git-diff-tree and symlinks Jochen Roemling
2005-05-29 15:06   ` Kay Sievers
2005-05-29 16:06     ` Jochen Roemling [this message]
2005-05-29 16:14       ` Sebastian Kuzminsky
2005-05-30  3:17       ` Sebastian Kuzminsky
2005-05-29 18:55     ` Junio C Hamano
2005-05-29 21:32     ` Petr Baudis

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=4299E88E.7090306@roemling.net \
    --to=jochen@roemling.net \
    --cc=git@vger.kernel.org \
    --cc=kay.sievers@vrfy.org \
    --cc=seb@highlab.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).