Hash out a solution for ChangeLog/NEWS at the Cauldron?

Siddhesh Poyarekar siddhesh@redhat.com
Wed Aug 5 14:29:00 GMT 2015


On Wed, Aug 05, 2015 at 02:22:17PM +0000, Joseph Myers wrote:
> An emailed patch doesn't have a commit id, assuming you mean the SHA1 hash 
> of the commit object generated by git; that depends on the committer email 
> and date, not just the author email and date, as well as the complete 
> state of the patched tree (not just the files modified by the patch) and 
> the parent commit objects.  For changes not involving the actual diff 
> itself I'd rather leave it to people to see the final commit on glibc-cvs 
> (and have the committer update patchwork manually if it can't be smarter 
> about detecting what's the same change) rather than having extra emails to 
> the list just for the sake of controlling patchwork.

Hmm, then I wonder how patchwork tracks the patches; it can't just be
the sha1sum.  I'll do some homework on this and get back to y'all.

Siddhesh



More information about the Libc-alpha mailing list