From: Andreas Ericsson <ae@op5.se>
To: Mikaël <mikael.donini@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: upgrading GIT from version 1.7.0.4 to 1.7.6.1.
Date: Mon, 19 Sep 2011 14:49:53 +0200 [thread overview]
Message-ID: <4E773A71.6020905@op5.se> (raw)
In-Reply-To: <1316435430491-6808156.post@n2.nabble.com>
On 09/19/2011 02:30 PM, Mikaël wrote:
>
> 1- Is it possible to have two GIT installations pointing on the same
> repositories?
>
The core structure and layout of a git repository hasn't changed
since may 2005, so it should work just fine provided you use any
git version that actually has a version number.
We've upgraded in a hodge-podge fashion at $dayjob. One of our
servers is still running 1.4.something. We've never even come close
to anything resembling a problem. It's actually a bit weird, since
we started using git in late 2005 and it's so far been the most
reliable and backwards-compatible piece of software we have in the
company pretty much ever since.
>
> 2- Do you have any suggestions, trips, hints and best practices in
> order to upgrade GIT in such a context?
>
Since you have such high demands on problem-free migration, I suggest
setting up a repo server running the new git (on the server side) and
having some people test against the new git with both old and new git,
as well as testing new git against the old servers.
Just get a backup first. I'm 99.9999999999999% sure you won't need it
because of anything git does, but better safe than sorry, eh?
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
Considering the successes of the wars on alcohol, poverty, drugs and
terror, I think we should give some serious thought to declaring war
on peace.
next prev parent reply other threads:[~2011-09-19 12:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-19 12:30 upgrading GIT from version 1.7.0.4 to 1.7.6.1 Mikaël
2011-09-19 12:43 ` Sverre Rabbelier
2011-09-19 12:49 ` Andreas Ericsson [this message]
2011-09-19 19:00 ` Jeff King
2011-09-19 21:26 ` Junio C Hamano
2011-09-19 22:44 ` Jeff King
2011-09-19 12: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=4E773A71.6020905@op5.se \
--to=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=mikael.donini@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).