Re: svn_client_patch()

kfogel@collab.net writes:

> IMHO we would do better to recommend that people install a patch
> program than take on the responsibility of maintaining such code
> ourselves.
>
> Someday, if/when we have a patch format that does more than
> conventional patch format, then we can consider a new tool.

I agree. We've talked about this idea in the past.

The reason we have 'svn diff' is because there's no easy way to use
plain old GNU diff to produce a patchfile describing every changed file.
(You'd have to run 'svn status', grep for 'M', cut out the filename,
and pass to GNU diff, along with some pattern to locate the text-base.
Yuck.)

But plain old GNU 'patch' works fine. You just run 'patch -p0 <
patchfile' as usual.

As Karl says, someday when 'svn diff' is able to produce a "next
generation" patch format that describes tree changes, then it makes
sense to have 'svn patch' which interprets the new format as well.

  - Ben, who is waiting for Tom Lord to start a project to define said
    format. :-)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Apr 6 06:41:17 2003