Question about features

[John Arbash Meinel]

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

Daniel Carrera wrote:
> Hi Tom,
> 
> Thanks for the info. Given what you say, I think that for my use case
> the right way to use bzr is to combine "bzr shelve" and "rsync".
> 
> I think I figured out how to use rsync to send work to the test server
> without creating a problem with branching and merging. instead of
> running "rsync" on the branch, I could run it on the parent directory:
> 
> $ cd ~/myProject
> $ ls
> branch-A/
> branch-B/
> trunk/
> $ rsync -avz -e ssh daniel at example.com:test/ .
> 
> So if I create a branch, that would go on a separate directory on the
> test server. This looks like a good solution. I can't see any drawbacks
> right now.
> 
> Daniel.
Well, you could always do:

  bzr commit
  bzr push [--overwrite?] / bzr upload
  bzr uncommit

So you copy across a tracked revision, and just overwrite it later when
you have a different one.

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

iEYEARECAAYFAkry8msACgkQJdeBCYSNAAPosACbBkRtne2FJfBlbeAz3/kBRZVj
mh8An2Pw+SVMH9hGpZ9AC97dHkDVIXYk
=nT89
-----END PGP SIGNATURE-----