From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Andreas Ericsson" <ae@op5.se>, Mikaël <mikael.donini@gmail.com>,
git@vger.kernel.org
Subject: Re: upgrading GIT from version 1.7.0.4 to 1.7.6.1.
Date: Mon, 19 Sep 2011 18:44:49 -0400 [thread overview]
Message-ID: <20110919224449.GC4056@sigill.intra.peff.net> (raw)
In-Reply-To: <7vwrd48bq8.fsf@alter.siamese.dyndns.org>
On Mon, Sep 19, 2011 at 02:26:55PM -0700, Junio C Hamano wrote:
> 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
next prev parent reply other threads:[~2011-09-19 22:44 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
2011-09-19 19:00 ` Jeff King
2011-09-19 21:26 ` Junio C Hamano
2011-09-19 22:44 ` Jeff King [this message]
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=20110919224449.GC4056@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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).