From: Jonathan Nieder <jrnieder@gmail.com>
To: Kacper Kornet <kornet@camk.edu.pl>
Cc: Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org, Sitaram Chamarty <sitaramc@gmail.com>
Subject: Re: [ANNOUNCE] Git v1.9-rc0
Date: Mon, 27 Jan 2014 10:58:29 -0800 [thread overview]
Message-ID: <20140127185829.GE27577@google.com> (raw)
In-Reply-To: <20140127175953.GA18041@camk.edu.pl>
Hi,
Kacper Kornet wrote:
> The change in release numbering also breaks down gitolite v2 setups. One
> of the gitolite commands, gl-compile-conf, expects the output of git --version
> to match /git version (\d+)\.(\d+)\.(\d+)/.
>
> I have no idea how big problem it is, as I don't know how many people
> hasn't migrate to gitolite v3 yet.
http://qa.debian.org/popcon.php?package=gitolite says there are some.
I guess soon we'll see if there are complaints.
http://gitolite.com/gitolite/migr.html says gitolite v2 is still
maintained. Hopefully the patch to gitolite v2 to fix this would not
be too invasive --- e.g., how about this patch (untested)?
Thanks,
Jonathan
diff --git i/src/gl-compile-conf w/src/gl-compile-conf
index f497ae5..8508313 100755
--- i/src/gl-compile-conf
+++ w/src/gl-compile-conf
@@ -394,8 +394,9 @@ die "
the server. If it is not, please edit ~/.gitolite.rc on the server and
set the \$GIT_PATH variable to the correct value\n
" unless $git_version;
-my ($gv_maj, $gv_min, $gv_patchrel) = ($git_version =~ m/git version (\d+)\.(\d+)\.(\d+)/);
+my ($gv_maj, $gv_min, $gv_patchrel) = ($git_version =~ m/git version (\d+)\.(\d+)\.([^.-]*)/);
die "$ABRT I can't understand $git_version\n" unless ($gv_maj >= 1);
+$gv_patchrel = 0 unless ($gv_patchrel =~ m/^\d+$/);
$git_version = $gv_maj*10000 + $gv_min*100 + $gv_patchrel; # now it's "normalised"
die "\n\t\t***** AAARGH! *****\n" .
next prev parent reply other threads:[~2014-01-27 18:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-16 21:03 What's cooking in git.git (Jan 2014, #03; Thu, 16) Junio C Hamano
2014-01-21 22:14 ` [ANNOUNCE] Git v1.9-rc0 Junio C Hamano
2014-01-22 12:53 ` Javier Domingo Cansino
2014-01-22 15:42 ` Junio C Hamano
2014-01-22 15:49 ` Stefan Näwe
2014-01-22 16:11 ` Junio C Hamano
2014-01-22 17:26 ` Vicent Martí
2014-01-22 18:10 ` Junio C Hamano
2014-01-22 20:30 ` Ken Moffat
2014-01-22 21:04 ` Junio C Hamano
2014-01-22 23:11 ` Ken Moffat
2014-01-23 2:09 ` Jeff King
2014-01-23 18:15 ` Junio C Hamano
2014-01-24 23:36 ` Jeff King
2014-01-27 22:56 ` Junio C Hamano
2014-01-28 0:04 ` Jeff King
2014-01-27 17:59 ` Kacper Kornet
2014-01-27 18:58 ` Jonathan Nieder [this message]
2014-01-28 12:28 ` Kacper Kornet
2014-01-30 22:20 ` Sitaram Chamarty
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=20140127185829.GE27577@google.com \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=kornet@camk.edu.pl \
--cc=sitaramc@gmail.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).