From mboxrd@z Thu Jan 1 00:00:00 1970 From: maximilian attems Date: Sat, 12 Feb 2005 12:41:06 +0000 Subject: Re: [KJ] [PATCH] drivers/isdn/hardware/eicon/*: convert to Message-Id: <20050212124106.GE23557@sputnik.stro.at> MIME-Version: 1 Content-Type: multipart/mixed; boundary="===============53407317107621699==" List-Id: References: <20050208084617.GI31996@rhum.iomeda.fr> In-Reply-To: <20050208084617.GI31996@rhum.iomeda.fr> To: kernel-janitors@vger.kernel.org --===============53407317107621699== Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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 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 --===============53407317107621699== Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline _______________________________________________ Kernel-janitors mailing list Kernel-janitors@lists.osdl.org http://lists.osdl.org/mailman/listinfo/kernel-janitors --===============53407317107621699==--