how could the handling of eol be improved to make it possible to
update a working copy of the svn repository via samba and compile it
on unix?
is an additional option to "svn up" a possibility, like "svn up
--eol-style=unix"?
or is it the best thing to just run "find ... -exec perl -i -pe
's/^M//g' {}" on the whole tree? i'm not sure if this confuses the
.svn directories contents .... i.e. include them or not?
if none of the above is a good solution:
what was the reason that the whole svn-repository has the property
set, and not only for the critical files, like makefiles?
--- Sander Striker <striker@apache.org> wrote:
> > From: solo turn [mailto:soloturn99@yahoo.com]
> > Sent: Wednesday, May 14, 2003 12:32 PM
>
> > i did the regular "svn up" on unix, compiled, and installed
> without
> > checking it (yes ... i know ... but it seemd 0.22.2, so safe?):
> now
> > it segfaults.
> >
> > so i tried to mount the drive via samba to nt, then do a "svn up"
> > from there.
> >
> > but the files updated have now different line-endings. and make
> > chokes.
> >
> > is there a simple possibility to tell "svn up" that it should not
> > touch line-ending style, or set it for the check out?
>
> Yeah, not set svn:eol-style.
>
> Btw, what you are doing is asking for trouble. You have checked
> out
> the working copy on platform A (*nix I presume) and are trying to
> update that very same working copy on platform B (win32). This
> blows
> right up when svn:eol-style is set to 'native'.
>
>
> Sander
__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed May 14 19:50:11 2003