Question about features

[Daniel Carrera]

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.


Tom Widmer wrote:
> Bazaar is quite bad at history editing of this kind I think. It's very 
> hard to uncommit changes that have already been incorporated into other 
> branches/looms/pipelines. Really, you just need to make another commit 
> that corrects the problem.
> 
> Bzr Rebase is the sum-total of built-in history rewriting support I 
> think: http://bazaar-vcs.org/Rebase . Unfortunately, I don't think this 
> supports rebasing backwards as such, which is what you need to be able 
> to uncommit changes that have already been branched from.
> 
>...
> 
> Note that both of these will tend to keep the history of all your 
> experiments, which you seemed to want to avoid.
> 
> BTW, Git has good history editing support.
> 
> Tom
> 
> 
>