Victor Mote wrote:
Jeremias Maerki wrote:
Well, for XML Files this is not a big problem usually, but
for Java files it usually is. But for text files in general,
native EOLs make life easier for certain people. Furthermore,
I don't see any such conventions documented (which doesn't
mean th
Jeremias Maerki wrote:
> Well, for XML Files this is not a big problem usually, but
> for Java files it usually is. But for text files in general,
> native EOLs make life easier for certain people. Furthermore,
> I don't see any such conventions documented (which doesn't
> mean there's no proj
I am also trying svn:keywords=Id. Many files have 'svn:keywords :
Author Date Id Revision', but my subversion manual suggests that of
those only Id is recognized, along with e.g. LastChangedDate. Id
comprises all known keywords.
Simon
On Thu, Aug 04, 2005 at 03:52:30PM +0200, Jeremias Maerki wrot
Maybe it would make sense to enable the "auto-props" feature of SVN
client. See the SVN config file (on Windows found in
%USERPROFILE%\Application Data\Subversion\):
### Set enable-auto-props to 'yes' to enable automatic properties
### for 'svn add' and 'svn import', it defaults to 'no'.
##
Well, for XML Files this is not a big problem usually, but for Java
files it usually is. But for text files in general, native EOLs make
life easier for certain people. Furthermore, I don't see any such
conventions documented (which doesn't mean there's no project standard):
http://xml.apache.org/f
fellow devs,
should this really be set to "native" ?
I just did a merge conflicts using SVN Tortoise (BTW, SVN is really
superior to CVS, Im really impressed!) and it changed the line endings
of CR+LF. I thought the Project standard was Unix style LF line endings.
So shouldn't this setting re
