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

[RFC] should these two topics graduate to 'master' soon?

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 28, 2017, 18:35 UTC
Message-ID
<xmqqshlxckr2.fsf@gitster.mtv.corp.google.com>

There are two topics that are marked as "Will cook in 'next'" for practically forever in the "What's cooking" reports. The world may have become ready for one or both of them, in which case we should do the merge not too late in the cycle.

* jc/merge-drop-old-syntax (2015-04-29) 1 commit
  This topic stops "git merge <message> HEAD <commit>" syntax that
  has been deprecated since October 2007 (and we have issued a
  warning message since around v2.5.0 when the ancient syntax was
  used).
* jk/no-looking-at-dotgit-outside-repo-final (2016-10-26) 1 commit
  This is the endgame of the topic to avoid blindly falling back to
  ".git" when the setup sequence said we are _not_ in Git repository.
  A corner case that happens to work right now may be broken by a call
  to die("BUG").

I am leaning toward including the former in the upcoming release, whose -rc0 is tentatively scheduled to happen on Apr 20th. I think the rest of the system is also ready for the latter (back when we merged it to 'next' and started cooking, there were still a few codepaths that triggered its die(), which have been fixed).

Opinions?
Next: Jonathan Nieder
Message 1 of 6 in “[RFC] should these two topics graduate to 'master' soon?”
  1. Junio C HamanoMar 28, 2017
  2. Jonathan NiederMar 28, 2017
  3. Jeff KingMar 28, 2017
  4. Junio C HamanoMar 30, 2017
  5. Stefan BellerMar 28, 2017
  6. Jon LoeligerMar 29, 2017

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.