Re: linux-next: Tree for Jan 25 (BROKEN suspend)

[Sedat Dilek]

On Mon, Jan 28, 2013 at 11:08 PM, Tejun Heo <tj@xxxxxxxxxx> wrote:
> Hello, Sedat.
>
> On Mon, Jan 28, 2013 at 11:06:11PM +0100, Sedat Dilek wrote:
>> 1. People should sent their patches concerning especially Linux-Next
>> fixes not only to LKML but also to <linux-next@xxxxxxxxxxxxxxx> (if
>> this is not known, pointing to James).
>>
>> 2. These patches for Linux-Next should contain a "-next" in their
>> subject-line (use 'git format-patch --subject-prefix="PATCH -next"
>> ...').
>>
>> Of course, I should have checked the MLs... but for me it was not
>> clear what was the root cause (which subsystem to blame)... I had only
>> some suspicions.
>
> Yeah, there was no way for you guys to easily discover that the
> problem has already been identified and fix pending.  I'll definitely
> try to cc linux-next cc'd on patches which fix problems in -next.
>
> Thanks a lot!
>

Hi Tejun,

BTW, I am reading MLs mostly offline!
That means I cannot grep for search-patterns I like (here: LKML).
Offline-reading also means, you get replies a lot of later.

NO, I am not planning to flood my INBOX with postings from LKML :-).

I highly suggest to send -next patches also to LKML.
Patchwork-service [1] makes it easy to get them in mbox-format for
easy application.

FYI: I am subscribed to linux-next ML and some other "smaller" linux-* MLs.

I dunno why Linux-Next hasn't join patchwork-service.
Stephen?

Also think of multiple postings of patches for the same issue :-).
...and lame and/or disappeared maintainers.

For a more better world...

- Sedat -

[1] marc.info/?l=linux-kernel
[2] http://marc.info/?l=linux-next
[3] https://patchwork.kernel.org/project/LKML/list/

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