On Mon, 15 Dec 2014 12:43:44 -0800 (PST)
Ashish Yadav <ashishyada...@gmail.com> wrote:
> I would like to upgrade my current git from version 126.96.36.199 to 2.2.0
> on Centos 6.5.
> Can I upgrade directly to 2.2.0 or or do I need an intermediate
> version to upgrade to first?
AFAIK, Git's object store format did not change, so no, you do not need
intermediate versions, but if you want to be sure, read the release
notes of intermediate releases -- they are freely available.
> Are there any gotchyas that I need to look out for when upgrading?
2.0 was a major version, so it did in fact change some defaults.
IIRC, it should only affect "local" (as opposed to "server-side") repos
though, but read the release notes.
> If needed, how can I rollback?
Install the 188.8.131.52 package back.
If you will detect any problems with the repos, you'll restore them
back from the nearest backup to the pre-upgrade state.
> What are the implication of upgrading git on the linux server? Is it
> transparent to the application and end user?
Should be. Contrary to some other notable DVCS systems, Git strives to
maintain backwards compatibility in its network protocol and object
store format as much as possible. But if you're unsure, the things to
do are very simple:
* Read the release notes;
* Set up a test box (virtualization is very cheap these days), upgrade
Git there, test how the older clients work with it, test how it
works with the existing (1.7.x) repo.
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/d/optout.