[prev in list] [next in list] [prev in thread] [next in thread] 

List:       bitkeeper-users
Subject:    RE: [Bitkeeper-users] some newbie questions re: cloning
From:       "Andy Chittenden" <achittenden () bluearc ! com>
Date:       2004-06-30 7:00:59
Message-ID: 89E85E0168AD994693B574C80EDB9C273F8D8B () uk-email ! terastack ! bluearc ! com
[Download RAW message or body]

Why not use "checkout: get" or "checkout: edit" (we use the latter) in your config file? See "bk help config-etc". If you're cloning a public repo, then I think you can have a /etc/BitKeeper/etc/config file on your machine that overrides the repo settings - don't think you can set this on a per user basis with a file in your ~/.bk directory though (which would be neat).

-- 
Andy, BlueArc Engineering 



> -----Original Message-----
> From: bitkeeper-users-admin@bitmover.com
> [mailto:bitkeeper-users-admin@bitmover.com]On Behalf Of Bryan 
> O'Sullivan
> Sent: 29 June 2004 20:31
> To: Robert P. J. Day
> Cc: bitkeeper users list
> Subject: Re: [Bitkeeper-users] some newbie questions re: cloning
> 
> 
> On Tue, 2004-06-29 at 14:05 -0400, Robert P. J. Day wrote:
> > 1) when i first clone a repository, i follow that up with a
> >     "bk -r co -q".  whenever i update my clone with a "bk pull",
> >     do i have to do the recursive checkout again?  i've heard two
> >     different stories from two different people, and i can't find
> >     an unambiguous answer in the docs.
> 
> I don't know what bk does with gfiles that have been changed 
> by a pull,
> but you'll definitely need to get copies of any new files.  I 
> use "bk -
> Rr get -Sq" for this.
> 
> > 2) one of the hosts on which i've created a clone only has a host
> >     and domain name of localhost.localdomain, with which bk clone is
> >     not terribly happy.
> 
> Set BK_HOST to something descriptive first.  You *really* don't want
> your machine to be called localhost.localdomain as far as BK is
> concerned.
> 
> 
> > 3) following up on 1), i want to clone one of the bkbits.net linux
> >     kernel repos, and let local developers get their own 
> clone from the
> >     local repo (to save bandwidth for the initial clone, 
> and for subsequent
> >     pulls.)
> > 
> >     so what i was planning was to clone to a local host and 
> just tell
> >     each developer to:
> > 
> >     $ bk clone http://localhost repo
> > 
> >     then they can do their own recursive checkout.
> 
> You can override the need for a recursive checkout by creating a file
> called /etc/BitKeeper/etc/config, and putting in the 
> following contents:
> 
> checkout: get!
> partial_check: yes!
> 
> 
> -- 
> Bryan O'Sullivan
> Software Tools
> PathScale, Inc.
> 
> _______________________________________________
> Bitkeeper-users mailing list
> Bitkeeper-users@bitmover.com
> http://bitmover.com/mailman/listinfo/bitkeeper-users
> To unsubscribe from this list, go to the above URL, follow 
> instruction at the bottom of the web page.
> 

_______________________________________________
Bitkeeper-users mailing list
Bitkeeper-users@bitmover.com
http://bitmover.com/mailman/listinfo/bitkeeper-users
To unsubscribe from this list, go to the above URL, follow instruction at the bottom of the web page.
[prev in list] [next in list] [prev in thread] [next in thread]