From: Pavel Roskin <proski@gnu.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: gitk shows an empty line between "Comments" and changed files
Date: Fri, 28 Oct 2005 18:45:03 -0400 [thread overview]
Message-ID: <1130539503.10531.43.camel@dv> (raw)
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:
> 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
next prev parent reply other threads:[~2005-10-28 22:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-27 17:30 gitk shows an empty line between "Comments" and changed files Pavel Roskin
2005-10-27 17:51 ` Junio C Hamano
2005-10-28 1:36 ` Pavel Roskin
2005-10-28 9:13 ` Junio C Hamano
2005-10-28 22:45 ` Pavel Roskin [this message]
2005-10-28 23:00 ` Linus Torvalds
2005-10-29 2:49 ` Junio C Hamano
2005-10-29 3:07 ` Linus Torvalds
2005-10-29 4:23 ` Pavel Roskin
2005-10-29 4:33 ` Linus Torvalds
2005-10-29 4:54 ` Pavel Roskin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1130539503.10531.43.camel@dv \
--to=proski@gnu.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).