On Fri, Aug 15, 2008 at 8:49 AM, Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx> wrote:
> Hi all,
>
> Today's linux-next merge of the kmemcheck tree got a conflict in
> arch/x86/kernel/traps_64.c between commit
> 4df9e510a9fda29aca71d8acac853b98aa6884d1 ("x86: coding style fixes to
> arch/x86/kernel/traps_64.c") from the x86 tree and commit
> 862849a36e6087faac6349de0b1bcc66ff98411b ("x86: add hooks for kmemcheck
> on x86_64") from the kmemcheck tree.
>
> All the includes got rearranged ... I fixed it up.
Hi Stephen,
Just out of curiosity: Do you have a script that produces these
messages? How hard would it be to include the "merge patch" (conflict
resolution) itself in this e-mail?
I think that would be a very helpful addition (if it can be done with
no hassle on your side), because it means that I could actually look
over it and give a comment if it looks wrong (with no hassle on my
side, looking up the merge commit, etc.).
But if it can't be done easily, then don't bother. The issues are
mostly trivial anyway. Thanks for doing this work!
Vegard
--
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
-- E. W. Dijkstra, EWD1036
--
To unsubscribe from this list: send the line "unsubscribe linux-next" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
