From: Larry McVoy <lm@bitmover.com>
To: Davidlohr Bueso A <dbueso@linuxchile.cl>,
linux-kernel@vger.kernel.org, '@ravnborg.org
Subject: Re: bk repository
Date: Thu, 20 May 2004 08:25:43 -0700 [thread overview]
Message-ID: <20040520152543.GB10634@work.bitmover.com> (raw)
In-Reply-To: <20040520073951.GA2210@mars.ravnborg.org>
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 see the repository in your browser use:
> http://linux.bkbits.net and select the linux-2.5 repository.
>
> The reason to keep the linux-2.5 name is simply that renaming the repository
> would cause parent information to be void for all people pulling
> from this directory.
>
> 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
--
---
Larry McVoy lm at bitmover.com http://www.bitkeeper.com
next prev parent reply other threads:[~2004-05-20 15:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-20 4:01 bk repository Davidlohr Bueso A
2004-05-20 7:39 ` Sam Ravnborg
2004-05-20 15:25 ` Larry McVoy [this message]
2004-05-20 18:04 ` Sam Ravnborg
2004-05-20 23:54 ` Ryan Anderson
2004-05-21 2:14 ` Randy.Dunlap
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=20040520152543.GB10634@work.bitmover.com \
--to=lm@bitmover.com \
--cc='@ravnborg.org \
--cc=dbueso@linuxchile.cl \
--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 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.