All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Franco <stratus@acm.org>
To: kernel-janitors@vger.kernel.org
Subject: [KJ] bitkeeper tree for kjt patchset?
Date: Tue, 14 Dec 2004 16:29:07 +0000	[thread overview]
Message-ID: <1103041747.8263.16.camel@localhost.localdomain> (raw)

[-- Attachment #1: Type: text/plain, Size: 822 bytes --]


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 ?

Reading all recent -mm announces we see that Andrew is merging acpi,
agpgart, arm, cifs and others bk trees. I think that he can merge bk-kjt
too and we'll see more testing of these patches posted at this list. 

Actually, the kjt 'release process' is post the patchset to lkml when
kjt maintainer feels that it's ok, no? IMO, it can be done the same way
but asking for Andrew merge bk-kjt before release -mm kernels adding
there (bk-kjt) only reviewed patches posted at this list. Comments?

If you think that it's a good idea and there's no server to setup it
(and i guess that bkbits won't be a problem), i can host it atm.

Hope that helps,
Gustavo Franco -- <stratus@acm.org>



[-- 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

             reply	other threads:[~2004-12-14 16:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-14 16:29 Gustavo Franco [this message]
2004-12-14 16:38 ` [KJ] bitkeeper tree for kjt patchset? Randy.Dunlap
2004-12-14 17:04 ` Matthew Wilcox
2004-12-14 17:31 ` maximilian attems
2004-12-14 17:46 ` walter harms

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=1103041747.8263.16.camel@localhost.localdomain \
    --to=stratus@acm.org \
    --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.