On Tue, 2013-08-20 at 20:36 -0500, Rob Landley wrote:
> On 08/20/2013 07:22:36 PM, Joe Perches wrote:
> > I'm also saying that the trivial tree should
> > have some visibility about whether or not a
> > patch or series will be handled by the trivial
> > maintainer or not.
[]
> > Jiri has not respon
On 08/20/2013 07:22:36 PM, Joe Perches wrote:
On Tue, 2013-08-20 at 19:10 -0500, Rob Landley wrote:
> The important question is does he want to handle patches that you're
> flipping out about not going in before the next merge window because
> they are SO IMPORTANT that the trivial tree must prom
On Tue, 2013-08-20 at 19:10 -0500, Rob Landley wrote:
> The important question is does he want to handle patches that you're
> flipping out about not going in before the next merge window because
> they are SO IMPORTANT that the trivial tree must promote them out of
> sequence.
You're misrea
On 08/20/2013 05:11:18 PM, Joe Perches wrote:
On Tue, 2013-08-20 at 16:49 -0500, Rob Landley wrote:
> On 08/20/2013 03:14:10 PM, Joe Perches wrote:
> > On Tue, 2013-08-20 at 15:02 -0500, Rob Landley wrote:
> > > On 08/19/2013 04:27:17 PM, Joe Perches wrote:
> > > > On Mon, 2013-08-19 at 23:22 +02
On Tue, 2013-08-20 at 15:24 -0700, Andrew Morton wrote:
> On Tue, 20 Aug 2013 15:11:18 -0700 Joe Perches wrote:
>
> > Andrew? Do you want to handle patches for defects that
> > are both obvious _and_ trivial?
>
> I look at everything!
Well, I guess I'll have to start cc'ing you on
the trivial
On Tue, 20 Aug 2013 15:11:18 -0700 Joe Perches wrote:
> Andrew? Do you want to handle patches for defects that
> are both obvious _and_ trivial?
I look at everything! If I like it and see that Jiri was cc'ed I try
to remember to cc him on the commit.
> > If it's trivial it's not time critical
On Tue, 2013-08-20 at 16:49 -0500, Rob Landley wrote:
> On 08/20/2013 03:14:10 PM, Joe Perches wrote:
> > On Tue, 2013-08-20 at 15:02 -0500, Rob Landley wrote:
> > > On 08/19/2013 04:27:17 PM, Joe Perches wrote:
> > > > On Mon, 2013-08-19 at 23:22 +0200, Jiri Kosina wrote:
> > > > > On Mon, 19 Aug
On 08/20/2013 03:14:10 PM, Joe Perches wrote:
On Tue, 2013-08-20 at 15:02 -0500, Rob Landley wrote:
> On 08/19/2013 04:27:17 PM, Joe Perches wrote:
> > On Mon, 2013-08-19 at 23:22 +0200, Jiri Kosina wrote:
> > > On Mon, 19 Aug 2013, Joe Perches wrote:
> > >
> > > > This is a 7 line patch that cor
On Tue, 2013-08-20 at 15:02 -0500, Rob Landley wrote:
> On 08/19/2013 04:27:17 PM, Joe Perches wrote:
> > On Mon, 2013-08-19 at 23:22 +0200, Jiri Kosina wrote:
> > > On Mon, 19 Aug 2013, Joe Perches wrote:
> > >
> > > > This is a 7 line patch that corrects logging defects that has had
> > no
> >
On 08/19/2013 04:27:17 PM, Joe Perches wrote:
On Mon, 2013-08-19 at 23:22 +0200, Jiri Kosina wrote:
> On Mon, 19 Aug 2013, Joe Perches wrote:
>
> > This is a 7 line patch that corrects logging defects that has had
no
> > reply from you for the last month.
> >
> > https://patchwork.kernel.org/p
On Mon, 2013-08-19 at 23:22 +0200, Jiri Kosina wrote:
> On Mon, 19 Aug 2013, Joe Perches wrote:
>
> > This is a 7 line patch that corrects logging defects that has had no
> > reply from you for the last month.
> >
> > https://patchwork.kernel.org/patch/2833648/
>
> This hasn't missed any Linus'
On Mon, 19 Aug 2013, Joe Perches wrote:
> This is a 7 line patch that corrects logging defects that has had no
> reply from you for the last month.
>
> https://patchwork.kernel.org/patch/2833648/
This hasn't missed any Linus' major release, as it has been submitted post
3.11 merge, right? (hin
On Mon, 2013-08-19 at 22:34 +0200, Jiri Kosina wrote:
> On Mon, 19 Aug 2013, Joe Perches wrote:
>
> > Patches submitted to the trivial address
> > triv...@kernel.org seem to go nowhere slowly.
> >
> > Jiri, do you have any actual plans to try to
> > pick up these patches, notify the submitters
>
On Mon, 19 Aug 2013, Joe Perches wrote:
> Patches submitted to the trivial address
> triv...@kernel.org seem to go nowhere slowly.
>
> Jiri, do you have any actual plans to try to
> pick up these patches, notify the submitters
> that the patches have been accepted or rejected,
> and forward them
Patches submitted to the trivial address
triv...@kernel.org seem to go nowhere slowly.
Jiri, do you have any actual plans to try to
pick up these patches, notify the submitters
that the patches have been accepted or rejected,
and forward them on when appropriate?
Otherwise, the patches sit for _m
15 matches
Mail list logo
