[$] Change IDs for kernel patches
For all its faults, email has long proved
to be an effective communication
mechanism for kernel development. Similarly, Git is an effective tool for
source-code management. But there is no real connection between the two,
meaning that there is no straightforward way to connect a Git commit with
the email discussions that led to its acceptance. Once a patch enters a
repository, it transitions into a new form of existence and leaves its past
life behind. Doug Anderson recently went to the ksummit-discuss list with
a
proposal to add Gerrit-style change IDs as a way of connecting the two
lives of a kernel patch; the end result may not be quite what he was asking
for.