git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: issue upgrading git from 1.8.2.1 to 2.8.0

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 22, 2016, 22:57 UTC
Message-ID
<xmqq37qdntew.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<CAGZ79kYt_D7F3Uq_bhDpJa6Hnc1xfazhU1oree_nM0xbgROqsQ@mail.gmail.com>
Stefan Beller <sbeller@google.com> writes:
> Although 1.8..2.8 is a lot, Git ought to stay compatible there.

In principle that is true, but there were deliberate backward incompatible changes at around 2.0 boundary, and those who followed along the upgrade paths were given warnings and advice messages to guide them to adjust their configurations during the incremental upgrade path. It is not all that surprising if somebody who jumped between the two versions in one hop didn't benefit from any such guidance, though.

Offhand, perhaps .git/config left by ancient versions and recent versions may differ in such a way that it affects the particular workflow deployed there?

Previous: Stefan BellerNext: Jeff King
Message 3 of 6 in “issue upgrading git from 1.8.2.1 to 2.8.0”
  1. Gennaro TorreApr 22, 2016
  2. Stefan BellerApr 22, 2016
  3. Junio C HamanoApr 22, 2016
  4. Jeff KingApr 22, 2016
  5. Jeff KingApr 23, 2016
  6. Jeff KingApr 23, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.