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

Re: gitk shows an empty line between "Comments" and changed files

From
PRPavel Roskin <proski@gnu.org>
Date
Oct 28, 2005, 22:45 UTC
Message-ID
<1130539503.10531.43.camel@dv>
In-Reply-To
<7v4q72xavz.fsf@assigned-by-dhcp.cox.net>
Hi, Junio!
On Fri, 2005-10-28 at 02:13 -0700, Junio C Hamano wrote:
Show 14 quoted lines
> Pavel Roskin <proski@gnu.org> writes:
> 
> > git-patch-id is only used by git-cherry.  git-cherry writes the second
> > SHA1 to some files in a temporary directory, but it never reads those
> > files, it only checks that they exist.
> 
> I do not oppose dropping the commit-id line from the default
> output, but having it optionally available would be useful in
> one application.  Somebody _could_ write a tool that does
> something like:
> 
>     git-rev-list ^$old_head $new_head |
>     git-diff-tree -p -m --stdin --with-commit-ids |
>     git-patch-id

Sounds good. Perhaps the commit IDs should have a prefix identifying them.

Another approach would be to use something slightly more elaborate than a pipe. If I understand correctly, the commit ID would be already known from the git-rev-list output. Passing commit IDs through patch-id without actually doing anything with them seems non-elegant. Maybe we could teach git-patch-id (or another script) to get patches by commit-id instead of using stdin?

-- 
Regards,
Pavel Roskin
Previous: Junio C HamanoNext: Linus Torvalds
Message 5 of 11 in “gitk shows an empty line between "Comments" and changed files”
  1. Pavel RoskinOct 27, 2005
  2. Junio C HamanoOct 27, 2005
  3. Pavel RoskinOct 28, 2005
  4. Junio C HamanoOct 28, 2005
  5. Pavel RoskinOct 28, 2005
  6. Linus TorvaldsOct 28, 2005
  7. Junio C HamanoOct 29, 2005
  8. Linus TorvaldsOct 29, 2005
  9. Pavel RoskinOct 29, 2005
  10. Linus TorvaldsOct 29, 2005
  11. Pavel RoskinOct 29, 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.