From: Mikaël <mikael.donini@gmail.com>
To: git@vger.kernel.org
Subject: upgrading GIT from version 1.7.0.4 to 1.7.6.1.
Date: Mon, 19 Sep 2011 05:30:30 -0700 (PDT) [thread overview]
Message-ID: <1316435430491-6808156.post@n2.nabble.com> (raw)
Dear All,
I am working for a company where several hundreds of people are working with
GIT ; in other words, GIT is a central tool for us since our working
processes are based on it.
Today, it is the time for us to upgrade from version 1.7.0.4 to 1.7.6.1 (the
latest stable).
It is important for us to work with the latest version since it corrects
defects that are very impacting for us.
The difficulty of this migration is that we can't afford migrations problems
(in order to maintain productivity and work).
That is the reason why I have a couple of questions:
1- Is it possible to have two GIT installations pointing on the same
repositories?
One of this installation would be GIT 1.7.6.1 used by a restricted number of
people (these people could be called 'beta-testers' of the new GIT version).
The other installation would be GIT 1.7.0.4 used by the other users (the
majority of users) with no impact on their productivity.
Once the beta-tests will be finished and successful, all the users will move
to GIT 1.7.6.1.
2- Do you have any suggestions, trips, hints and best practices in order to
upgrade GIT in such a context?
Thanks a lot for your answers.
Best Regards,
Mikaël Donini.
--
View this message in context: http://git.661346.n2.nabble.com/upgrading-GIT-from-version-1-7-0-4-to-1-7-6-1-tp6808156p6808156.html
Sent from the git mailing list archive at Nabble.com.
next reply other threads:[~2011-09-19 12:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-19 12:30 Mikaël [this message]
2011-09-19 12:43 ` upgrading GIT from version 1.7.0.4 to 1.7.6.1 Sverre Rabbelier
2011-09-19 12:49 ` Andreas Ericsson
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=1316435430491-6808156.post@n2.nabble.com \
--to=mikael.donini@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).