Re: Svn as a changeset engine.

       kfogel:

> It'd be nice if our metadata system were flexible enough to
> handle [a particular kind of merge histories].

Change sets are especially useful for communicating between
organizations who can not, in general, be presumed to use the same
revision control system in-house.

In other words, merge histories for change-based management need to be
distributed and storage-manager independent. I've found that it
works out nicely to store this information in regular text files,
within project trees themselves.

You _might_ also want to have change history meta-data in svn
repositories to help with merging that is internal to a single
repository -- but don't confuse that with the more general,
inter-organizational kind of merging.

        Noel:

> Could this functionality be better served by wrapping
> Subversion?

I think the answer to that question, for almost all bindings of "this
functionality", is always going to be "yes".

-t

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Oct 15 20:59:55 2002