> I went off and did some research. Among other things, I ran
> my eyeballs over some dump files. I've learned that dump
> files don't normally contain diffs at all -- when a node is
> changed in a revision, the revision contains an entire copy
> of that node.
I suspect you are already aware of this, but in 1.1 when you create a dump
file you can specify --deltas to create a so-called "deltified" dump file.
I think these deltas are the raw internal Subversion storage format, not
exactly the same as a diff.
Regardless, I thought I recalled that when this was talked about
previously, it was just the overall dumpfile structure and meta-information
that we were interested in. I thought there was going to be a mime-type or
something like that to indicate that the file contents were being expressed
as a patch-compatible diff, or some other format?
When I think of this feature, my assumption is you would work within your
normal WC, doing edits, svn add/copy/move/delete etc.... Then, rather than
do a commit, you could create one of these "action-diffs" to capture it
all. Presumably you would then do a revert or something to get back to
scratch. Later, the action-diff could be applied to another WC, conflicts
resolved etc., and then finally perhaps committed to the repository using
normal svn mechanisms.
You seem to envision something different, such as performing commits to the
action-diff as well. How do you envision doing the commit, what would the
UI be?
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Sep 28 02:20:18 2004