mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Ryan Anderson <ryan@michonline.com>
Cc: lm@work.bitmover.com, dbueso@linuxchile.cl,
	linux-kernel@vger.kernel.org, '@ravnborg.org
Subject: Re: bk repository
Date: Thu, 20 May 2004 19:14:58 -0700	[thread overview]
Message-ID: <20040520191458.191496a3.rddunlap@osdl.org> (raw)
In-Reply-To: <20040520235438.GB18544@michonline.com>

On Thu, 20 May 2004 19:54:38 -0400 Ryan Anderson <ryan@michonline.com> wrote:

| On Thu, May 20, 2004 at 08:25:43AM -0700, Larry McVoy wrote:
| > On Thu, May 20, 2004 at 09:39:51AM +0200, Sam Ravnborg wrote:
| > > On Thu, May 20, 2004 at 12:01:02AM -0400, Davidlohr Bueso A wrote:
| > > > When will the 2.6 branch be added to the bitkeeper resository?
| > > It's alrweady there, but with a bit mis-leading name.
| > > bk://linux.bkbits.net/linux-2.5
| 
| [...]
| 
| > > To my knowledge there is no possibility to symlink two repositories, so
| > > both names could live in parrallel for a while??
| > 
| > Sure there is and it's done.
| > 
| > root@hostme:/repos/l/linux# ls -l
| > total 20
| > drwxrwxr-x   17 linux    1000         4096 May 20 05:29 linux-2.4
| > drwxrwxr-x   20 linux    1000         4096 May 20 07:27 linux-2.5
| > lrwxrwxrwx    1 root     root            9 May 20 08:24 linux-2.6 -> linux-2.5
| > drwxrwxr-x   20 root     root         4096 May 10 17:40 lm
| > drwxrwxr-x   16 linux    root         4096 Apr 16 23:43 vger
| > drwxrwxr-x    5 linux.ad 1000         4096 Mar 28  2002 www
| 
| Wouldn't it make sense to avoid the need to do this in the future?
| 
| Specifically, make a tree named "linux" available - that's always the
| Linus tree.
| 
| Create linux-2.6/2.8/3.0/3.2 etc as they are handed off to maintainers
| *other* than Linus?
| 
| Or some combination that makes sense.  It just seems weird to me to need
| to continually change the name of the main development tree.

Continually, as in every 2-3 years?  I don't see much of a problem
here unless the cycle length changes.

--
~Randy

      reply	other threads:[~2004-05-21 22:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-20  4:01 Davidlohr Bueso A
2004-05-20  7:39 ` Sam Ravnborg
2004-05-20 15:25   ` Larry McVoy
2004-05-20 18:04     ` Sam Ravnborg
2004-05-20 23:54     ` Ryan Anderson
2004-05-21  2:14       ` Randy.Dunlap [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=20040520191458.191496a3.rddunlap@osdl.org \
    --to=rddunlap@osdl.org \
    --cc='@ravnborg.org \
    --cc=dbueso@linuxchile.cl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm@work.bitmover.com \
    --cc=ryan@michonline.com \
    /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

all inboxes | Powered by JetHome®