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

Re: Thoughts and open questions on patch/dump unification

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: 2004-09-16 19:04:52 CEST

"Eric S. Raymond" <esr@thyrsus.com> writes:

> OK. We are talking about two fundamentally different concepts here.
> There is probably a place for both of them in the Subversion universe,
> so I'm going to propose terminology to distinguish them.

*Thank You!*

> You get to keep the term "action diff" for your single-changeset creature
> with no log text, date, or author. An action diff, alone, can only be
> applied to a working copy. Besides change bands in the patch(1) style,
> it may include file adds/renames/deletes. (I'm not clear on whether it
> makes sense for action diffs to include property operations.)

Yes, it does.

> What I'm talking about, I'll now rename a "history diff". A history
> diff may consist of one or more action diffs in sequence, each with
> associated log text, author, and date. History diffs apply to
> repositories. A dumpfile is a history diff meant to be applied to an
> empty repository.

Sounds great.

> To do the decentralized-development thing, action diffs don't suffice.
> We need history diffs. I view the design and implementation of action
> diffs as interesting primarily because it's a building block for doing
> history diffs.

That's correct. Action diffs are *just* 'svn diff' + tree operations
and property changes.

> I hope this clarifies matters.

Quite. Thanks again.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Sep 16 19:07:16 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.