public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: linus@atomide.com, Andrew Morton <akpm@osdl.org>,
	Len Brown <len.brown@intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Trying to coordinate moving subprojects to git
Date: Mon, 2 May 2005 09:32:07 -0700	[thread overview]
Message-ID: <20050502163206.GA16366@atomide.com> (raw)

Hi Linus, Andrew & Len,

Here's a slightly modified repost of my earlier message
that got eaten by the mailing list filter :)

I'm trying to summarize some earlier dicussions on how to
coordinate moving BK projects over to git. This is probably
of interest to many other subprojects as well.

My main problem is where to host git trees for subprojects.

Here's how I see the move to git happening for various
subprojects:

- Somebody is rumored to offer a git project site soonish.[1]
  When that is available, subprojects can configure git
  trees there.
  
- Meanwhile, there should also be a BK repo for the latest
  kernel changes available soon.[2] Once that is available,
  it can be used for updating various trees.

Now I wonder if anybody has more news on the following:

- Who is working on setting a site available for git
  projects, and when is that site estimated to be available?
  
- Is anybody working on mirroring git changes in a BK tree?

I'm afraid I can't be much of help here setting up these sites
with my 128Kbps upstream speed...

Regards,

Tony

[1] http://lkml.org/lkml/2005/4/23/27
[1] http://lkml.org/lkml/2005/4/26/32

             reply	other threads:[~2005-05-02 16:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-02 16:32 Tony Lindgren [this message]
2005-05-02 16:56 ` Trying to coordinate moving subprojects to git Tony Lindgren

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=20050502163206.GA16366@atomide.com \
    --to=tony@atomide.com \
    --cc=akpm@osdl.org \
    --cc=len.brown@intel.com \
    --cc=linus@atomide.com \
    --cc=linux-kernel@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