From: maximilian attems <janitor@sternwelten.at>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] [PATCH] drivers/isdn/hardware/eicon/*: convert to
Date: Sat, 12 Feb 2005 12:41:06 +0000 [thread overview]
Message-ID: <20050212124106.GE23557@sputnik.stro.at> (raw)
In-Reply-To: <20050208084617.GI31996@rhum.iomeda.fr>
[-- Attachment #1: Type: text/plain, Size: 1054 bytes --]
On Wed, 09 Feb 2005, Armin Schindler wrote:
> On Tue, 8 Feb 2005, Christophe Lucas wrote:
> > Armin Schindler (armin@melware.de) wrote:
> > > Hi,
> > >
> > > who is sending/committing those patches to BK tree?
> > >
> > > Armin
> >
> > Now, no one.
dooh - your are wrong.
you'll need some more patience.
janitorial stuff is not critical,
so needs its time to get accepted.
>
> Now? And in the furture?
> What is the kernel-janitors' way to send patches?
>
> Anyway, I will send the patch for this...
>
> Armin
thanks for doing that,
Domen Puncer <domen@coderock.org> is current kj Maintainer,
but i guess that latest peak of activity may have well
interferred with his own vacations.
so you'll probably do him a favour. :)
anyway when he is back he'll collect the patches out of the list
and will send out a new -kj patchset against latest with the not
applied ones and after testing, he'll push the patches upstream.
maintainers are free to take the patches per themselves.
gregkh or davej does it frequently.
hope that explains..
a++ maks
[-- Attachment #2: Type: text/plain, Size: 167 bytes --]
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
http://lists.osdl.org/mailman/listinfo/kernel-janitors
next prev parent reply other threads:[~2005-02-12 12:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-08 8:46 [KJ] [PATCH] drivers/isdn/hardware/eicon/*: convert to Christophe Lucas
2005-02-08 12:11 ` Armin Schindler
2005-02-08 13:44 ` Christophe Lucas
2005-02-09 7:41 ` Armin Schindler
2005-02-12 12:41 ` maximilian attems [this message]
2005-02-12 13:34 ` Armin Schindler
2005-02-12 15:32 ` maximilian attems
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050212124106.GE23557@sputnik.stro.at \
--to=janitor@sternwelten.at \
--cc=kernel-janitors@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.