Re: Patch command execution

[Partially addressed to Daniel Berlin, partially to list.]

IMHO, if you (or anyone) wants to implement an internal patch library
that handles the subset of patch svn needs, plus the extensions
discussed, go for it! Removing that external dependency, while
getting better behavior, would be great. But, a couple of thoughts:

   - Needs a very thorough test suite. We can't afford bugs in
     `patch'. :-)

   - Is this the best use of time right now? I mean, the only problem
     (so far) is the failure to handle already-applied hunks in the
     ideal way. Meanwhile, we've got a huge bug database with lots of
     more serious stuff...

Naturally, your time is your own, and an internalized patch library
would be quite welcome. But if you have a set of N things you're
considering working on, maybe it's worth asking if this is the most
important thing in that set?

-Karl

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:37:05 2006