Re: Improved patch format - SoC

> All I'm saying is, if you get the distributed rcs people involved again
> to design a One True Portable Changeset Format, I wouldn't be surprised
> to see the process bog down as everybody attempts to add their own
> requirements that have little to do with Subversion. Everybody, that
> is, who isn't too busy peddling their own existing patchset formats, of
> which I imagine there are some.
>

Yes, but I think that if someone comes with some logical improvements to
the "lowest common denominator" that unidiff is, many just start using it.

The two things that need to be added to unidiff so that it can be a base
to an improved format are: Copies and deletions. And perhaps that's as
easy as:

--- subversion/include/svn_config.h (revision 24348)
+++ subversion/include/svn_config2.h (working copy)
@@ -146,8 +146,8 @@
 /** Read configuration data from @a file (a file or registry path) into
  * @a *cfgp, allocated in @a pool.
[...]

... and ...

--- subversion/include/svn_config.h (revision 24348)
+++*deleted* (working copy)
[...]

(no space between the '*' and the '+' for differentiating this from a
file called "*deleted*" =) )

Everything else can be added in ignoreable chunks: properties, binary
diffs, repository information, etc.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Apr 3 02:14:05 2007