All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Robert Love <rml@tech9.net>
Cc: Larry McVoy <lm@bitmover.com>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.4 and BitKeeper
Date: Thu, 14 Mar 2002 11:40:57 -0700	[thread overview]
Message-ID: <3C90EEB9.5050007@candelatech.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0203140141450.4725-100000@freak.distro.conectiva>	<3C904437.7080603@candelatech.com> <20020313224255.F9010@work.bitmover.com>	 <3C90E994.2030702@candelatech.com> <1016130404.4289.5.camel@phantasy>



Robert Love wrote:

> On Thu, 2002-03-14 at 13:19, Ben Greear wrote:
> 
> 
>>I did a clone with this.  However, I see no files, only
>>directories.  The files do seem to be in the SCCS directories,
>>but I don't know how to make them appear in their normal place.
>>
> 
> Uh that is how BK works.  The files are stored.  Try
> 
> 	bk -r co
> 
> to get all the files.  Omit the `-r' to check out only the current
> directory.


Ahh, that did fix the problem.  It must be configured differently
where I work, because I do not have to do the bk -r co command there.


> 
> There are some decent tutorials and such on bitmovers[1] page.
> 
> [1] http://www.bitmover.com


I went though them once...looks like I need a refresher course!

Thanks,
Ben


> 
> 	Robert Love
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 
> 


-- 
Ben Greear <greearb@candelatech.com>       <Ben_Greear AT excite.com>
President of Candela Technologies Inc      http://www.candelatech.com
ScryMUD:  http://scry.wanfear.com     http://scry.wanfear.com/~greear



  reply	other threads:[~2002-03-14 18:41 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-14  4:42 Linux 2.4 and BitKeeper Marcelo Tosatti
2002-03-14  6:33 ` Ben Greear
2002-03-14  5:36   ` Marcelo Tosatti
2002-03-14  6:37   ` David S. Miller
2002-03-14  6:42   ` Larry McVoy
2002-03-14  7:54     ` Alex Riesen
2002-03-14 15:46       ` Larry McVoy
2002-03-14 18:10         ` Alex Riesen
2002-03-14 18:19     ` Ben Greear
2002-03-14 18:26       ` Robert Love
2002-03-14 18:40         ` Ben Greear [this message]
2002-03-14 22:56           ` Mark Frazer
2002-03-15 11:10     ` David Woodhouse
2002-03-15 16:04       ` Larry McVoy
2002-03-15 16:17         ` Stelian Pop
2002-03-15 17:58         ` Linus Torvalds
2002-03-15 18:16           ` Jeff Garzik
2002-03-15 18:27             ` Linus Torvalds
2002-03-15 18:47               ` Larry McVoy
2002-03-17  0:39                 ` Daniel Phillips
2002-03-17  5:42                   ` Mike Fedyk
2002-03-18 16:47               ` [PATCH] 2.5.7-pre2 IDE 22a Martin Dalecki
2002-03-15 18:39           ` Linux 2.4 and BitKeeper Larry McVoy
2002-03-15 19:01             ` Linus Torvalds
2002-03-15 19:10               ` Larry McVoy
2002-03-15 19:20                 ` Linus Torvalds
2002-03-15 19:30                   ` Larry McVoy
2002-03-16  0:31                     ` Andreas Ferber
2002-03-16  1:02                       ` Andreas Dilger
2002-03-15 16:10       ` David Woodhouse
2002-03-15  4:35 ` Stephen Torri

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=3C90EEB9.5050007@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm@bitmover.com \
    --cc=rml@tech9.net \
    /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.