I'm not done yet writing the design document regarding the patch
format but here's attached a first draft. I'd like to get a feedback,
especially on the sole use of svndiff1 (line 32) within the patch. I
don't think this turns to be an issue as a client will need the svn
patch subcommand to apply the patch anyway, which implies a fresh
client release (at least post 1.4.x), which implies svndiff1
capability.
As for the implementation, I'll be able to use some existing code to
parse subversion protocol bytes. Though, I'm planning to tweak the
code to fit with such an offline/one-way use (no negotiation, no
response, restrict to the editor command set, so forth). svn patch
would just read svn protocol bytes out from the patch, and drive the
client's editor from that. Should anyone have a better idea instead
of or to enhance this one, I'd be glad to hear and work it out :-)
I'm working on a python test in parallel, soon coming.
Cheers,
Charles
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jun 22 21:45:24 2007