Tangential question about bzr concepts

[Martin Pool]

On 29 Mar 2006, "Andrew S. Townley" <andrew.townley at bearingpoint.com> wrote:
> 
> Hi Guys,
> 
> This isn't specifically a bzr question, but I'm trying to see if bzr (or
> parts thereof) could be used as the solution.
> 
> If you were prepared to accept the risk of not keeping version history,
> could the logic in bzr as a distributed VCS be used to assist in keeping
> peer-to-peer replicas (say, of a filesystem) in sync.  Maybe there's
> something to do this already, but rsync doesn't merge changes to files.
> 
> What I want is that if I've made a change to a text file (maybe on both
> systems), those changes would be merged and propagated to all of the
> hosts, meaning that I wouldn't really lose any data.  I know this
> problem has been solved for databases with multi-master capabilities,
> but I was wondering if something like the merge stuff in bzr would
> assist in doing it for filesystems.
> 
> This was just something I was wondering about, and I know it isn't
> directly related, but thanks for the tolerance :)
> 
> Thanks in advance,

You can use bzr to do this.  

I'm not sure what you mean by "accept the risk of not keeping version
history".  If you mean "I want to merge without keeping version history"
then it's not really in our scope, and not keeping any history will
restrict the kind of merges you're able to do.  If you strongly want to
not keep history then you might like to look at Unison, Coda, etc.
(Well, they do keep history, but of a more restricted type.)

-- 
Martin