Actually, thinking about it, I was wrong here, only committers are concerned.
So only them must use a Subversion 1.8 client
Jacques
Le 27/07/2016 à 12:35, Jacques Le Roux a écrit :
Actually, since we get new committers now and then and their are able to create new files I have a warning every
Actually, since we get new committers now and then and their are able to create new files I have a warning every 6 months which says "Check Java
files, have all svn:eol-style=native" (I totally forgot that because I assume the machine knows it and warns me ;))
I could extend that to all files (a
Okay, it seems from the documents that you provided we will not feel the
impact, and this would actually improve the situation by ensuring that
files are checked in with the right EOL and we don't need to go back and
forth over the correct EOL encoding.
If you didn't face any problems while conver
Hi Taher,
Actually a svn repo *always* stores files in *nix EOL format. You don't have to
worry about that.
How it is when you checkout or update your working copy depends on the platform
you use
This is clearly explained at the bottom of
http://svnbook.red-bean.com/en/1.7/svn.advanced.props.
Hi Jacques,
What does this setting imply? Does it imply that all users regardless of
their OS will push LF characters for EOL to the repository? And does it
also mean that If I checkout a working copy that I will not find strange
EOL characters (^M) in my files?
Taher Alkhateeb
On Wed, Jul 27,
BTW Taher (and All actually)
I guess you need to at least svn up the build.gradle files, and later other
*.gradle when I'll have set their svn properties.
HTH
Jacques
Le 27/07/2016 à 10:50, Jacques Le Roux a écrit :
It's not a workaround, it's how things should work according to Apache
Sub
BTW if nobody disagree, I'd like to follow the suggestion I made in the last
message of the linked thread.
In other words, use
http://subversion.apache.org/docs/release-notes/1.8.html#repos-dictated-config
http://blogs.collab.net/subversion/the-road-to-repository-dictated-configuration-day-2-aut
It's not a workaround, it's how things should work according to Apache
Subversion documentation, but I missed one part.
I was there before, see http://markmail.org/message/fnvmt4fapgowtaux
So please wait I also need to set the svn:properties of the *.gradle files and
commit them in the repo
J
Hi Jacques and All,
I noticed in your commit r1754071 you mentioned a workaround for the EOL
issue generated from your editor which I cannot understand. Right now I'm
trying to commit some work for cleaning up the libraries and again I face
the EOL issue (I updated my config file for subversion).
