Tom Lord <lord@regexps.com> writes:
> 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.
Yeah, that's what I was thinking too.
> 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.
It would be better to not distinguish between the two kinds of
merging, if we can avoid it; or treat them the same, just that the
"internal" merge might have more data available to it (but in the same
format as usual).
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Oct 15 21:12:11 2002