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.
"SteveKing" <steveking@gmx.ch> writes:
> I'd like to make a request for a new/missing function:
>
> svn_client_patch()
>
> as the 'reverse' of svn_client_diff().
> The GNU patch program is not installed on every
> system and it has a _lot_ of options to set.
> Also it would be more user friendly if an 'svn patch'
> would exist because it wouldn't be necessary to
> learn the parameters of another tool.
>
> What would be great is if svn_client_patch would also
> take a log message and include that in the diff file.
> Then the svn_client_patch would extract the log
> message and store it somewhere (in a file or registry)
> and on the next commit the log message from the
> diff file would get automatically filled in...
>
> I haven't found an issue for such a function - shall I
> write one?
>
> Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Apr 6 02:54:04 2003