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

Re: What's cooking in git.git (Mar 2015, #08; Mon, 23)

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 24, 2015, 23:37 UTC
Message-ID
<xmqqd23y3r2m.fsf@gitster.dls.corp.google.com>
In-Reply-To
<xmqqmw338khu.fsf@gitster.dls.corp.google.com>
Junio C Hamano <gitster@pobox.com> writes:
Show 8 quoted lines
> Here are the topics that have been cooking.  Commits prefixed with
> '-' are only in 'pu' (proposed updates) while commits prefixed with
> '+' are in 'next'.
>
> This cycle is turning out to be a "shoot for product excellence"
> release.  About half of the commits that have been merged to the
> 'master' so far have also been merged to 'maint' and v2.3.4 has been
> tagged.

I've merged a few more topics to 'next' and hopefully will push the result out in a few hours.

Some topics that are in 'next' but not in 'master' are high-impact ones that I'd feel more comfortable if we cooked them there for a bit more, and am planning to merge them (if there are no issues discovered in the meantime, of course) after this cycle finishes, but for others, I'm hoping to merge them to 'master' before we tag the -rc0 preview release.

Please give them a good beating and report any regressions you find.
Thanks.
Previous: Junio C Hamano
Message 10 of 10 in “What's cooking in git.git (Mar 2015, #08; Mon, 23)”
  1. Junio C HamanoMar 23, 2015
  2. Junio C HamanoMar 24, 2015
  3. Jeff KingMar 24, 2015
  4. Junio C HamanoMar 24, 2015
  5. Junio C HamanoMar 24, 2015
  6. Jeff KingMar 26, 2015
  7. Junio C HamanoMar 24, 2015
  8. Jakub NarębskiMar 25, 2015
  9. Junio C HamanoMar 25, 2015
  10. Junio C HamanoMar 24, 2015

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.