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

Re: What's in git.git (stable)

From
Alex Riesen <raa.lkml@gmail.com>
Date
Mar 31, 2007, 11:54 UTC
Message-ID
<20070331115458.GC4377@steel.home>
In-Reply-To
<7v1wj5ycx5.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano, Sat, Mar 31, 2007 11:34:14 +0200:
Show 6 quoted lines
> 
> If you can remind me of patches that are "must have"s for 1.5.1
> that I've missed, that would be very nice.  We've broken "git
> am" and "git rebase" (without --merge) on 'master' branch for
> people who has i18n contents after 1.5.0 but they should be
> fixed now.

We still have absolutely broken merge-recursive WRT rename/rename conflicts in intermediate trees.

> Please, remember that the key word for this weekend is "make
> 1.5.1 NO WORSE than 1.5.0".  IOW, the focus is on obvious
> regression fixes.
It is "no worse", but doesn't "pretty bad" count?
Previous: Junio C HamanoNext: Junio C Hamano
Message 2 of 3 in “What's in git.git (stable)”
  1. Junio C HamanoMar 31, 2007
  2. Alex RiesenMar 31, 2007
  3. Junio C HamanoApr 5, 2007

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.