What's missing from our changelogs [LWN.net]

What's missing from our changelogs

Posted Jul 25, 2013 8:02 UTC (Thu) by lacos (guest, #70616)
In reply to: What's missing from our changelogs by nevets
Parent article: What's missing from our changelogs

This. Message-IDs are very important, and it's good that some public archives support search by msgid. For example, the URL format for gmane is

http://news.gmane.org/find-root.php?message_id=2013071818...

A further improvement is storing the original subject (including the "bag of tags" part) of the patch email (if the patch was posted to and applied from a list) as a "pseudo header". This helps identifying a series using just the git commit log (due to the patch numbering being captured).

What I miss is some way to save cover letters as standalone, no-code-change commits.

to post comments

What's missing from our changelogs

Posted Jul 25, 2013 8:32 UTC (Thu) by johill (subscriber, #25196) [Link] (1 responses)

There's an easier redirect one for gmane:

http://mid.gmane.org/20130718184712.GA4786@redhat.com

What's missing from our changelogs

Posted Jul 25, 2013 8:44 UTC (Thu) by lacos (guest, #70616) [Link]

Interesting! Thanks!

(Still I like to end up immediately in the threaded / frames interface.)

What's missing from our changelogs

Posted Jul 25, 2013 12:39 UTC (Thu) by hmh (subscriber, #3838) [Link] (1 responses)

You could have the entire patch series as a temporary (topic) branch, and the cover letter as the [empty] merge commit log message, and you can do that right now.

This works well only when the patch stack is going in through the same tree, obviously.

As for notes, their out-of-band nature will complicate a secure workflow somewhat, but it should be possible to do it.

What's missing from our changelogs

Posted Jul 26, 2013 0:53 UTC (Fri) by aliguori (guest, #30636) [Link]

Empty commits dont survive a rebase which makes it hard to use for topic branches.