From: walter harms <wharms@bfs.de>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] bitkeeper tree for kjt patchset?
Date: Tue, 14 Dec 2004 17:46:15 +0000 [thread overview]
Message-ID: <41BF26E7.7000502@bfs.de> (raw)
In-Reply-To: <1103041747.8263.16.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 718 bytes --]
Matthew Wilcox wrote:
> On Tue, Dec 14, 2004 at 02:29:07PM -0200, Gustavo Franco wrote:
>
>>What do you think of a bk repository for kjt? I did a search and i
>>didn't see anything related with this topic, am i missing something ?
>
>
> For the kind of patches in -kj, a BK tree wouldn't be a great idea.
> It's the wrong usage model for janitor patches.
>
>
Hi ppl,
i agree that BK ist not the way to go since KJ patches are more random,
and will later go to other maintainer of drivers/subsystems like that
(IMHO).
But i agree with Gustavo that submitters need a better overview what is
going on. in a way that would allow to maintains to tkae notice of
changes (no idea who that can be done)
re,
walter
[-- 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
prev parent reply other threads:[~2004-12-14 17:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-14 16:29 [KJ] bitkeeper tree for kjt patchset? Gustavo Franco
2004-12-14 16:38 ` Randy.Dunlap
2004-12-14 17:04 ` Matthew Wilcox
2004-12-14 17:31 ` maximilian attems
2004-12-14 17:46 ` walter harms [this message]
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=41BF26E7.7000502@bfs.de \
--to=wharms@bfs.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).