Re: svn_client_patch()

> > > IMHO we would do better to recommend that people install a patch
> > > program than take on the responsibility of maintaining such code
> > > ourselves.

Please be kind if I'm asking here stupid questions, but isn't subversion
already doing something similar like patch when doing merges?

> > > Someday, if/when we have a patch format that does more than
> > > conventional patch format, then we can consider a new tool.

That was what I was asking for - a patch format which also includes
the log message. Ok, I admit it isn't a feature which can't wait but
I would definitely mark it as 'nice to have' and therefore maybe
even file an issue for post-1.0?

> 1. Property diff application.

Never noticed that properties weren't applied with patch. Now
that would be something that even might mark the gnu patch
useless for some scenarios. Imagine if someone does some
changes which _need_ some changes in the properties to
get the whole patch to work - then the sent in patch file
can't be applied...

> 2. Conflict markers!! Regular 'patch' will just crap out on
> conflicting hunks -- this behavior is poo. 'svn patch' could
> behave just like 'svn merge', except from a stream source
> instead of a repository. :-) Now tell me that isn't Goodness!

I vote for that!

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 09:11:51 2003