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

AW: Patch files

From: Jens Geyer <jgx_at_vsx.net>
Date: Thu, 3 Nov 2011 18:18:02 +0100

> It may be that the problem you're seeing is because of the different
> EOLs used on Windows and Linux. Especially if you've also set the
> svn:eol-style to 'native'.

Indeed, the EOL-style is set to native in my case

But ...

1. If it were only for CRs, the patch command usually spits out " (Stripping trailing CRs from patch.)" which is not the case.
2. As a TSVN user who is creating a patch using TSVN, I cannot be sure that my patch really works on someone else's machine, who is not using (T)SVN. And because it seems that I can't trust on that feature, it is effectively useless to me in such cases.

From my (maybe limited) understanding, the intention of a patch file is exactly that: To be able to send change sets to someone else without the need to commit them before, because I may not be allowed to commit, or I just don't want to do that right now. Therefore I would conclude that a patch file should be "cross-platform-able" by design, independent on what the EOL-style may be. However, this seems not to be the case, and thus, a possible conclusion could be, that a patch file created by (T)SVN is not necessarily a correct patch file, only something similar.

Or am I completely wrong on that?

Interestingly, the (T)SVN "Apply Patch" feature is quite tolerant regarding patch files, it consumes nearly anything without complaints. Coincidence?

BTW, the comment I referred to is here, but there seem to be a lot of people that seem to have the same problem.

What do you think?


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-11-03 18:19:15 CET

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.