Description Juris Sudmalis 2013-09-21 06:09:31 EDT

When creating a patch of any project that is connected to an SVN repository, the files in the resulting patch are in wrong order. Let's say, I had a directory structure like this:
/abc/bar.java
/abc/foo.java
/def/bar.java
/def/foo.java

if all of these files were modified and I created a patch via Eclipse, it rarely orders them correctly, usually the order is somewhat random, for example, it could order the /abc/ and /def/ directories in opposite direction and keep the file order (if lucky enough):
/def/bar.java
/def/foo.java
/abc/bar.java
/abc/foo.java
or the other way around:
/abc/foo.java
/abc/bar.java
/def/foo.java
/def/bar.java
It does, however, keep directories of the same name in one group, i.e. it will never put /def/ between 2x /abc/.

The problem for me (and possibly many others) is that when posting such a patch to a github gist and later updating it, the history log is all garbled even if all you did was change 1 line in 1 file, because the file order is completely different every time you create a patch (provided you have enough files, of course).

If I make the patches via command line (svn diff on project root) everything is fine, so to me it's obvious the problem is in Eclipse.

I have observed this problem for quite a while, but until now I didn't have a real reason to have the files in the correct order other than readability.

P.S. not sure if this is a Subversive-only problem, maybe other VCS have the same thing.