Re: Reinventing the wheel? (Patch format for exchanging tree modifications)

I have to admit, I've all but given up on the problem of creating a
patch format that interoperates with other version control systems.
We tried to do this once... we even created a mailing list with
representives from different systems. The list proved fruitless. It
turns out VC systems have different models for representing
changesets, and the list turned into Tom Lord telling everyone else
how his model was 'best' and how we should all rewrite our systems to
match his. :-/

If it turns out that cross-vc-system interoperability is "low hanging
fruit", then that's great news. But please be wary... please don't
sabotage our own functionality to get it.

BTW, I believe that SVK's patch format is basically 'svn diff' plus a
big binary hunk thrown at the end, which is just perl's serialization
of an editor drive. (Is that right?)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Apr 1 13:53:15 2007