[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bd6139dc0804161243i5e5c973aia0cf2d5ec19079fa@mail.gmail.com>
Date: Wed, 16 Apr 2008 21:43:47 +0200
From: "Sverre Rabbelier" <alturin@...il.com>
To: "Andrew Morton" <akpm@...ux-foundation.org>
Cc: "Adrian Bunk" <bunk@...nel.org>, git@...r.kernel.org,
linux-kernel@...r.kernel.org, jmorris@...ei.org,
viro@...iv.linux.org.uk, w@....eu, david@...g.hm,
sclark46@...thlink.net, johnpol@....mipt.ru, rjw@...k.pl,
tilman@...p.cc, Valdis.Kletnieks@...edu, lkml@....ca,
davem@...emloft.net, jesper.juhl@...il.com,
yoshfuji@...ux-ipv6.org, jeff@...zik.org, netdev@...r.kernel.org,
davidn@...idnewall.com
Subject: Re: Reporting bugs and bisection
On Wed, Apr 16, 2008 at 9:02 PM, Andrew Morton
<akpm@...ux-foundation.org> wrote:
> Sounds like an interesting project.
Thank you :).
> Well yes. One outcome of the project would be to tell us what changes we'd
> need to make to our processes to make such data gathering more effective.
I defenitly agree here, the command's reliability could be increased
by always specifying bugfixes in a certain way. 'fixed-bug:' for
example should be very recognizable.
> Of course, we may not actually implement such changes. That would depend
> upon how useful the output is to us.
Ah yes, free will and whatnot. Then again, everybody already does
'signed-off-by:', if there's an easy command in git to mark a bugfix,
it would increase the odds of people using it. Perhaps something like
'git commit -b 10256" which would then automagically append a
predefined message to the commit users would feel more inclined?
Cheers,
Sverre Rabbelier
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists