On Sat, Jul 19, 2014 at 9:31 AM, Steven Rostedt rost...@goodmis.org wrote:
On Fri, Jul 18, 2014 at 06:22:15PM -0400, Theodore Ts'o wrote:
And then think very hard about which patches people need to see in
order to be able to evaluate a patch. For example, if you have patch
1 out of a series
On Fri, Jul 18, 2014 at 06:22:15PM -0400, Theodore Ts'o wrote:
And then think very hard about which patches people need to see in
order to be able to evaluate a patch. For example, if you have patch
1 out of a series which adds a new function, and then patches 2
through 1000 modify a
On Fri, Jul 18, 2014 at 05:38:30PM +0300, Andrey Utkin wrote:
Is there script for automated checkpatch.pl get_maintainers.pl
git send-email for range of commits? I see none. Would it be welcome
to submit such one to kernel tree?
Too much automation can be a really bad thing. You **really**
On Sat, Jul 19, 2014 at 11:35:45AM +0800, Hillf Danton wrote:
On Sat, Jul 19, 2014 at 9:31 AM, Steven Rostedt rost...@goodmis.org wrote:
On Fri, Jul 18, 2014 at 06:22:15PM -0400, Theodore Ts'o wrote:
And then think very hard about which patches people need to see in
order to be able to
Is there script for automated checkpatch.pl get_maintainers.pl
git send-email for range of commits? I see none. Would it be welcome
to submit such one to kernel tree?
--
Andrey Utkin
___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
On Fri, 2014-07-18 at 15:47 -0700, Joe Perches wrote:
On Fri, 2014-07-18 at 18:22 -0400, Theodore Ts'o wrote:
and get_maintainers.pl.
I think checkpatch
Umm, make that get_maintainer...
is pretty good about cc'ing mostly the
right folk by default.
