[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: 3 way merge algorithm

From: Torsten Rueger <torsten.rueger_at_hiit.fi>
Date: 2004-04-30 12:57:08 CEST

On 29 Apr 2004, at 20:59, kfogel@collab.net wrote:
> It's too bad that a university (of all things!)
We can release code, just a year after writing. That off course is
little use in ongoing development. Exceptions can be made, if interest
is there, but it isn't.

> Do you know why they have this policy, if there's any chance of
> changing it?
It's department policy and the fact that we can publish at all is seen
as a great benefit. In other departments it's different.

> Would it help if some of us sent letters saying how it
> could make a real difference to our project if the restrictions were
> lifted? I'd certainly be happy to do so, if you think it would.

Thank's for the offer. But I don't think it would help. Our project is
about data synchronisation, and while I have long seen the basic
equivalence of source control and (multi-peer) synchronisation, my boss
has not. So improving a source control system is at this point not on
the agenda. I have been, and will continue to work on the issue though.

> You probably have a lot to read already in your job, so sorry for
> piling a new URL on your plate :-).

No way, thanks for read. It's actually a different problem, one we
haven't even addressed or thought about yet.
It sounds like a thorough and workable plan you have there.

The algorithm I had there avoids the topic of externalised patch
formats completely. So it can't apply any patches to different versions
and the whole topic you solved there, is never addressed. Good to see
it though.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Apr 30 12:57:36 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.