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

Re: svn commit: r919460 - filtering svn patch targets

From: Stefan Sperling <stsp_at_elego.de>
Date: Wed, 10 Mar 2010 22:43:27 +0100

On Wed, Mar 10, 2010 at 08:58:24PM +0100, Stefan Kng wrote:
> On 10.03.2010 19:14, Julian Foad wrote:
> >>Yes, I would also need to know which paths the patch wants to modify,
> >>and then later I want to tell the API which of those paths it should
> >>actually modify.
> >>This is to let the user choose which paths to modify and which ones not.
> >
> >OK, well the issue #3434 didn't mention that. Since you already have a
> >patch implementation which does what you want, could you show us the API
> >definition (at least) for this part of it? That would help a lot, since
> >then we wouldn't have to guess about what you want :-)
> It's basically a class with methods like:
> * ParsePatchfile
> * GetCount //returns the number of paths affected
> * GetPath(int index) // returns the affected path
> * PatchPath(int index, TCHAR * target) // applies the patch for the
> path and saves the result in 'target'
> The names of the class methods are actually a little bit different,
> but that's pretty much what we have right now and what we need.

What about if you just parse the patch using the diff parser
we have in libsvn_diff? Would that be enough?
See this file for details:
We could make those functions public if you want.

Another thing: Why do you need to apply the patch to some tempfile?
Why is the preview of the patched result really necessary?
Why not just show the user the patch? When reviewing what a patch
does, it's much easier to look at the patch itself rather than the
patched result -- at least from my point of view, I don't know if your
users are different.

If you agree to these points, we could drop the svn_client_patch() API
change again.

Received on 2010-03-10 22:44:06 CET

This is an archived mail posted to the Subversion Dev mailing list.