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

Re: [PATCH] Fix bad usage of mkpath in builtin-branch.sh

From
Junio C Hamano <junkio@cox.net>
Date
Oct 25, 2006, 22:51 UTC
Message-ID
<7v3b9cko0b.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<20061025224313.GM20017@pasky.or.cz>
Petr Baudis <pasky@suse.cz> writes:
Show 7 quoted lines
>> +
>> +test "$ret" = 0 && git-diff-tree --summary --root --no-commit-id HEAD
>> +
>>  exit "$ret"
>
> Yes, this might be a good idea, although after the commit is perhaps too
> late.

Before the commit I thought we have git-status output in the commit log buffer.

Ah,...

We had that old issue of "'M foo' cannot tell content or mode changes (or both)", and people suggested "M+" and such which were rejected because Porcelains and people's scripts depended deeply on "diff --name-status" output being stable.

Previous: Petr Baudis
Message 7 of 7 in “Fix bad usage of mkpath in builtin-branch.sh”
  1. Fix bad usage of mkpath in builtin-branch.shLars Hjemli, Oct 24, 2006
  2. Junio C HamanoOct 24, 2006
  3. Petr BaudisOct 24, 2006
  4. Junio C HamanoOct 25, 2006
  5. Junio C HamanoOct 25, 2006
  6. Petr BaudisOct 25, 2006
  7. Junio C HamanoOct 25, 2006

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.