wn problems. I am not about
to tell anyone that using only LF is always safe for all
projects, my only contention was that it can be safe for some,
that EOL issues are not what they once were (at least not on
Windows).
--
Geoff Worboys
Telesis Computing
Geoff Worboys wrote:
>> (Forcing users to deal with the reply-to stuff on this list
>> is something of a pain don't you think. As if I need the list
>> copy and a CC copy. Never mind...)
Ryan Schmidt wrote:
> No, we don't think so.
> http://subversion.apach
ion is viable for many
projects these days.
Obviously if you are going to continue to use old *nix based
scripts that remain vulnerable after all these years then
of course you must work-around such limitations, for which
the features of svn are very convenient.
--
Geoff Worboys
Telesis Computing
makes a
mistake and accidently commits a file with CRLF it is an
easy fix to resolve ... although most Windows software wont
care even if you don't bother to fix it.
--
Geoff Worboys
Telesis Computing
st?) newer (Windows) software is much more tolerant.
If, as in Nico's case, you stick with LF (no Windows EOL)
then your files will continue to work with the unnecessarily
fussy *nix tools and also with most modern Windows software.
--
Geoff Worboys
Telesis Computing
here interested in looking-at/experimenting-with the
powershell script let me know, I am happy to share it. Does
this list accept attachments or can that be done only via
private email?
Thanks again.
--
Geoff Worboys
Telesis Computing
o the correct blocks of output ... etc.
If it was purely a text file then many things would be more
obvious but being a mix of binary and text the use of \n
delimiters needs to be careful (and should be explicit).
Thanks for your response, most appreciated.
--
Geoff Worboys
Telesis Computing
d be good to know what I was
doing. ;-)
Hmmm... big post for my first post. Hope that's okay.
--
Geoff Worboys
Telesis Computing
