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

Re: augmented diff design patch format

From: Ben Collins-Sussman <sussman_at_red-bean.com>
Date: 2007-06-22 23:53:10 CEST

Hi Charles, great to see you on the list. Here are my first thoughts.

Your spec talks about the 'svn diff' command being able to produce
'default', 'unidiff', and 'svnpatch' output. My question is: why do
we need both 'default' and 'unidiff' modes? Seems like the only
difference is whether or not property diffs are displayed. The
current output of 'svn diff' seems to be a combination of the two
modes at the moment (unidiff, but also shows property diffs)... is
there a compelling reason to change this? It would be a lot simpler
to just have 'svn diff' continue producing what it does now, and then
add one extra mode to produce our new 'svnpatch' format containing
editor commands.

My only other thought is that hey, yeah, I guess that using a chunk of
svn-protocol is definitely a nice way of representing an
editor-drive.... but is it optimal for us? Does it have too much
baggage specific to client/server stuff? I'm just wondering if some
other serialization format might be simpler.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jun 22 23:52:58 2007

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.