LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Roland McGrath <roland@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86_64 ia32 syscall restart fix
Date: Fri, 29 Feb 2008 18:17:37 +0100 [thread overview]
Message-ID: <20080229171737.GA10604@elte.hu> (raw)
In-Reply-To: <alpine.LFD.1.00.0802290855230.17889@woody.linux-foundation.org>
* Linus Torvalds <torvalds@linux-foundation.org> wrote:
> So the kernel is probably fairly odd in generally not asking for any
> fixed-format stuff at all (like the GNU changelogs do) but instead
> writing a small human-readable novella ;)
i think it's also a good learning tool. Subscribing to git-commits-head
might be more useful to a newbie these days than subscribing to lkml :-/
and one area where commit messages are totally important IMO is bug
forensics. For every regression we find we try to put in the commit ID
that broke it. Information like that is vital to have a good (and
objective) picture about how bugs get into and get out of the kernel and
it also alerts us to change/improve infrastructure if certain categories
of bugs happen too often.
Ingo
next prev parent reply other threads:[~2008-02-29 17:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-29 3:57 [PATCH] x86_64 ia32 syscall restart fix Roland McGrath
2008-02-29 15:52 ` Ingo Molnar
2008-02-29 16:26 ` Linus Torvalds
2008-02-29 16:45 ` Ingo Molnar
2008-02-29 17:03 ` Linus Torvalds
2008-02-29 17:17 ` Ingo Molnar [this message]
2008-02-29 17:37 ` Ingo Molnar
2008-02-29 21:02 ` Andrew Morton
2008-02-29 21:20 ` Ingo Molnar
2008-03-01 5:48 ` [stable] " Greg KH
2008-02-29 22:42 ` Roland McGrath
2008-02-29 23:18 ` Linus Torvalds
2008-03-07 22:56 ` [PATCH] x86_64 ptrace orig_ax on ia32 task Roland McGrath
2008-03-07 23:18 ` Linus Torvalds
2008-03-08 1:37 ` Roland McGrath
2008-03-10 19:19 ` Chuck Ebbert
2008-03-10 19:48 ` Linus Torvalds
2008-03-10 20:01 ` Roland McGrath
2008-03-11 9:32 ` Ingo Molnar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080229171737.GA10604@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=roland@redhat.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).