Reorganise repository layout

John Arbash Meinel john at arbash-meinel.com
Fri Mar 16 15:33:17 GMT 2007


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Daniel Silverstone wrote:

...

>> So from your suggestions I did the following:
>> $ cd ~/bzr
>> $ bzr branch talks/aps-200704
>> bzr: ERROR: Not a branch: /Users/ram/bzr/talks/aps-200704/
>> I get the same error for the other directory.
>> Does anybody have any ideas where I'm going wrong?
> 
> Sounds like you've been confusing the others by calling ~/bzr/talks a
> 'repository' as it sounds like you've actually got a branch there.
> 
> One way would be to simply branch the entire thing, remove aps-200704
> from one and lsc-200703 from the other. This is inefficient but easy.
> 
> The other way I can think of involves using the new
> dirstate-with-subtrees work which is experimental to split each of your
> talks off into a branch of its own.
> 
> I'm not sure which you'd feel safer doing. Also others may now be able
> to spot the issue and suggest better ideas than I can come up with.
> 
> D.

There are a couple issues here, just based on what I'm assuming Adam
would want.

To start with, this does most of what you want:

$ bzr branch repo project1
$ cd project1
$ bzr rm project2 project3
$ bzr mv project1/* .
$ bzr rm project1
$ bzr commit -m "Splitting project1 into its own branch".

(#repeat for the other 2 projects).

At this point, you can "bzr branch project1" and it will only build the
files for 'project1'.

There is a small issue with it still pulling over some history for those
other projects. (It won't copy *new* commits, but it will copy stuff
that has already been committed, because that is part of the ancestry).

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFF+ri9JdeBCYSNAAMRAoPHAKCdmyZP+TF98cyYyiNYBS+VLmQDxgCdHX7Y
Ow67Ztz1xpSAROU5Tg4sOOU=
=Qjrh
-----END PGP SIGNATURE-----



More information about the bazaar mailing list