Date: Fri, 29 Feb 2008 18:17:37 +0100
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
Message-ID: <20080229171737.GA10604@elte.hu>
References: <20080229035707.EAE862700FD@magilla.localdomain> <20080229155207.GC27248@elte.hu> <alpine.LFD.1.00.0802290814320.17889@woody.linux-foundation.org> <20080229164510.GA6850@elte.hu> <alpine.LFD.1.00.0802290855230.17889@woody.linux-foundation.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <alpine.LFD.1.00.0802290855230.17889@woody.linux-foundation.org>
User-Agent: Mutt/1.5.17 (2007-11-01)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1026
Lines: 23


* 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/