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

Re: [PATCH] show changed tree objects with recursive git-diff-tree

From
Junio C Hamano <junkio@cox.net>
Date
May 21, 2005, 02:11 UTC
Message-ID
<7vsm0hpbub.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<Pine.LNX.4.62.0505202131520.4397@localhost.localdomain>

Although I do not have immediate objections to what it tries to do, I have to think about the intent of the patch and its ramifications.

However, I think the patch operates at the wrong level if you are basing on the tip of Linus tree. With the new diff core, you do not filter like this:

- char *newbase = malloc_base(base, path1, pathlen1); + char *newbase; + if (!silent && !generate_patch) + diff_change(mode1, mode2, sha1, sha2, base, path1); + newbase = malloc_base(base, path1, pathlen1);

I'd just say "if (!silent)" there. The updated diff_change _should_ do the right thing regardless of generate_patch value you have there, because it is already told about it with diff_setup(), and it knows not to say silly things when we are generating patch.

Previous: Nicolas PitreNext: Linus Torvalds
Message 2 of 9 in “show changed tree objects with recursive git-diff-tree”
  1. show changed tree objects with recursive git-diff-treeNicolas Pitre, May 21, 2005
  2. Junio C HamanoMay 21, 2005
  3. Linus TorvaldsMay 21, 2005
  4. Nicolas PitreMay 23, 2005
  5. Junio C HamanoMay 25, 2005
  6. Nicolas PitreMay 25, 2005
  7. Junio C HamanoMay 25, 2005
  8. Linus TorvaldsMay 21, 2005
  9. Junio C HamanoMay 21, 2005

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.