Re: upgrading GIT from version 1.7.0.4 to 1.7.6.1.

From: Jeff King <peff@peff.net>
Date: Sep 19, 2011, 22:44 UTC
Message-ID: <20110919224449.GC4056@sigill.intra.peff.net>
In-Reply-To: <7vwrd48bq8.fsf@alter.siamese.dyndns.org>

On Mon, Sep 19, 2011 at 02:26:55PM -0700, Junio C Hamano wrote:

Show 12 quoted lines

> Jeff King <peff@peff.net> writes:
> 
> > [2] I suspect a similar thing happened with turning on packed refs
> >     (around the v1.4.4 era?), but I didn't dig around for details.
> 
> Also when bisecting down to really ancient versions of git, you may get
> complaints from the configuration reader. E.g.
> 
>     $ rungit v1.0.0 ls-files
>     fatal: bad config file line 78 in .git/config
>     $ sed -n 78p .git/config
>     [remote "git-gui"]

Ugh, yeah. There are similar problems with some specific config options (one I run into a lot these days is that "pager.foo" used to complain if the value was non-boolean, but now you can put in an arbitrary command). But those only bite you if you start using the new config options (which you obviously are not doing until after you upgrade).

But your example will bite anyone because git generates remote config like that by default.

Anyway, most of that is only applicable if you are crossing several major version boundaries, or are using ancient versions of git. I'm pretty sure that v1.7.0.x -> v1.7.6.x is pretty safe.

-Peff