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

Re: Bug: file named - on git commit

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Feb 4, 2013, 19:32 UTC
Message-ID
<20130204193248.GB15552@google.com>
In-Reply-To
<7v8v742cwh.fsf@alter.siamese.dyndns.org>
Junio C Hamano wrote:
>            (some may be too minor to be worth backproting, for
> example).

Yes, this is the part I was asking for help with. Backporting is easy but convincing the release team and upgrade-averse sysadmins to like the result generally isn't. Occasional nominations of the form "this change is important in my workflow" could help.

Continuing to stick to fixes to very severe bugs that stand out plus a random assortment of problems people have reported can also work fine, though.

Thanks, Jonathan

Previous: Junio C Hamano
Message 10 of 10 in “Bug: file named - on git commit”
  1. Rene MoserJan 28, 2013
  2. Matthieu MoyJan 28, 2013
  3. Duy NguyenJan 28, 2013
  4. Thomas RastJan 28, 2013
  5. [CLOSED FIXED] Bug: file named - on git commitRene Moser, Jan 28, 2013
  6. Jonathan NiederJan 28, 2013
  7. Junio C HamanoJan 28, 2013
  8. Junio C HamanoJan 28, 2013
  9. Junio C HamanoFeb 4, 2013
  10. Jonathan NiederFeb 4, 2013

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.