How to communicate with upstream sources intelligently

[John Arbash Meinel]

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

Jari Aalto+usenet wrote:
> * Wed 2006-06-28 John Arbash Meinel <john AT arbash-meinel.com>
> * Message-Id: 44A30B88.2000604 AT arbash-meinel.com
>>>     TRUNK => 1.0 => 1.1
>>>
>> You could do:
>>
>> cd ~
>> bzr init-repo --trees project
>> cd project
>> bzr init TRUNK-1.0
>> cd TRUNK-1.0
>> (untar the tarball)
>> bzr add; bzr commit -m "release 1.0"
>>
>> cd ..
>> bzr branch TRUNK-1.0 TRUNK-1.1
>> etc.
> 
> Ok, I see. Now they are complete separate. I was thinking "svn
> switch", but bzr does not yet have it if I rememeber correct.
> 
> Hm. How do I diff between 1.0 and 1.1 to see what's changed
> in the model you presented?
> 
> Jari

That depends more if you *want* to work in an SVN style. The repository
can be a remote object, and you only have lightweight checkouts locally.
In that situation, bzrtools does have a 'switch' which changes the
target of a lightweight checkout.

I can explain the process, but it takes more work on your part to
maintain everything. I would recommend the above process to start with.

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

iD8DBQFEozXVJdeBCYSNAAMRAiVHAKDGkR22RKHWht56FmcsxB/nC7ZHfgCg1oRj
uKS8PcQW7nuxx8NpVFMjYTQ=
=y51k
-----END PGP SIGNATURE-----