Re: Thoughts and open questions on patch/dump unification

Mark Phippard <MarkP@softlanding.com>:
> > I have precious little interest in seeing Subversion become a
> > decentralized version control system. So "syncing repositories"
> > transforms in my mind to "unidirectionally syncing read-only slave
> > repositories with a single master repository", and for that purpose
> > the existing dump format, as-is, is perfect.

> Obviously our main problem currently is that we are essentially doing a
> lot of work without any version control because we have no place to
> commit. All we can do currently is make patches on a regular basis and
> archive them. Yes, we could solve the problem by having an EBCDIC branch
> in the actual repository, but lets just assume that is not an option.

Heh. First you say you have little interest in seeing Subversion
become a decentralized version control system. then you present a use
case that really wants exactly that.

Your "place to commit" should be a local repository, and your way
of shipping fully-baked EBCDIC changes to the main project should
be *exactly* the kind of repo sync I have been attempting to describe.

IMHO...

-- 
		Eric S. Raymond
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org