LKML Archive on
help / color / mirror / Atom feed
From: "Ilpo Järvinen" <>
To: Jan Engelhardt <>
Cc: ael <>, LKML <>
Subject: Re: git tree urls
Date: Sat, 9 Feb 2008 01:36:39 +0200 (EET)	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <Pine.LNX.4.64.0802082353390.26116@fbirervta.pbzchgretzou.qr>

On Fri, 8 Feb 2008, Jan Engelhardt wrote:

> On Feb 8 2008 22:34, ael wrote:
> >
> >Sure, I looked there in some depth. But some/most are special purpose or
> > 'locals'. One needs a map for the "main" repositories...
> Indeed, a page on with the most important repositories
> would be helpful.
> Well, to start:
> torvalds/linux-2.6.git	Mainline
> jgarzik/netdev-2.6.git	Network devices
> davem/net-2.6.git	Networking
> x86/linux-2.6-x86.git	x86
> mchehab/v4l-dvb.git	V4L and DVB
> bunk/trivial.git	Spellos, typos and the obvious
> But it's not that easy. netdev-2.6.git for example regularly gets merged
> into net-2.6.git, so you get a fairly recent netdev tree by choosing
> either netdev or net.

Also explaining the rotation of those two trees would be useful (I
suppose some other subsystems too use somewhat similar rotation). I.e., 
net-2.6.26.git will eventually be opened and new development should be 
based on it (whenever such tree with a future version number is 
available), and that tree then becomes net-2.6.git once 2.6.25 is out. 
net-2.6.git is usually for fixes only unless merge window is currently 
open. These things come up quite often.


      reply	other threads:[~2008-02-08 23:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-08 11:37 ael
2008-02-08 13:38 ` Andi Kleen
2008-02-08 15:10   ` Jiri Kosina
2008-02-08 18:59 ` Stefan Richter
2008-02-08 19:14 ` Jan Engelhardt
2008-02-08 22:34   ` ael
2008-02-08 22:58     ` Jan Engelhardt
2008-02-08 23:36       ` Ilpo Järvinen [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \
    --subject='Re: git tree urls' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).