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 - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.htmlReceived on Sat Oct 29 08:45:44 2005
This archive was generated by hypermail 2.1.8 : 2005-10-29 08:45:48 EST