On Thu, Feb 28, 2008 at 10:12 AM, Reedick, Andrew <jr9445_at_att.com> wrote:
>
>
> > From: Nathan Nobbe [mailto:quickshiftin_at_gmail.com]
> > Sent: Thursday, February 28, 2008 9:54 AM
> > To: Ryan Schmidt
> > Cc: subversion-users
> > Subject: Re: pre-revprop-change
> >
> >
> > i dont see anything here that specifically says, svn:eol-style
> > cannot be used as a revision property
> > http://svnbook.red-bean.com/en/1.0/ch07s02.html
>
> Even if you add it as a revision property, I doubt it would have any
> effect on anything.
>
>
> > i must have some disconnect regarding usage of these
> > properties.. is there no way to say, i want all files
> > in this repository, beneath this directory to have their
> > eol managed by the subversion?
>
> Checkout the dir in question and run 'svn setprop svn:eol-style native' on
> the desired files, followed by a check-in.
>
> It would be nice to have a 'svn propset' that works on URLs (with an
> implicit commit) in much the same way that 'svn mv' or 'svn copy' do.
>
>
> > what about new files? if i create a file and add it to
> > the repository, without specifying the svn:eol-style
> > property on it, will the eol style on the file not be
> > managed by the repository? thats ridiculous, considering
> > users may be creating files on their own.. that's asking
> > users to get involved in administration tasks; eww.
>
> You can set the config file in ~/subversion/.config or
> %userprofile%\application data\subversion\config to automatically set the
> svn:eol-style for _newly_ created files.
>
> However, it's left as an exercise to the reader to actually push a
> standardized config file to all your subversion clients. So you might want
> to make friends with your unix/windows system admin. =/
im thankful for the replies from everyone.
however i am not happy with the picture thats being painted.
it seems to me, id be better off to create a post-commit hook that simply
runs dos2unix or something similar.
can anyone argue against that ?
-nathan
Received on 2008-02-28 16:49:43 CET