From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH] gitweb: fill in gitweb configuration by Makefile
Date: Mon, 31 Jul 2006 09:38:26 +0200 [thread overview]
Message-ID: <eakc16$p77$1@sea.gmane.org> (raw)
In-Reply-To: 20060731070819.GD16364@admingilde.org
Martin Waitz wrote:
> On Sun, Jul 30, 2006 at 06:20:26PM -0700, Junio C Hamano wrote:
>>
>> I think the other parts are sensible but I am not sure if we
>> want to report the version of git distribution (your patch), or
>> the version of git binary the cgi script happens to use (the
>> current implementation).
>
> hmm, right.
> Well, now that gitweb is included with GIT I think that they will
> be in sync on many sites, but of course that's not guaranteed.
>
> Shall I send a new patch without that change?
There are currently two version variables in gitweb: the version of the
script, and the version of git binaries used. They might be different.
But now that gitweb is bundled with git, perhaps we could use compile-time
git version as gitweb version, i.e.
our $version = "@@GIT_VERSION@@";
while leaving $git_version as is, i.e.
our $git_version =
qx($GIT --version) =~ m/git version (.*)$/ ? $1 : "unknown"
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2006-07-31 7:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-30 22:37 [PATCH] gitweb: fill in gitweb configuration by Makefile Martin Waitz
2006-07-31 1:20 ` Junio C Hamano
2006-07-31 7:08 ` Martin Waitz
2006-07-31 7:38 ` Jakub Narebski [this message]
2006-08-01 19:34 ` Martin Waitz
2006-07-31 8:14 ` Luben Tuikov
2006-07-31 3:57 ` Luben Tuikov
2006-07-31 6:41 ` Junio C Hamano
2006-07-31 7:22 ` Martin Waitz
2006-07-31 9:38 ` Johannes Schindelin
2006-07-31 16:59 ` Luben Tuikov
2006-07-31 21:33 ` Jon Loeliger
2006-07-31 6:55 ` 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='eakc16$p77$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
/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).