-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Fri, 29 Oct 2004 15:44, Michael Conrad wrote:
> So, one thing that always drove me nuts is the issue of editing alternately
> between windows and unix.
Amen!
<snip>
> 2: "ASCII Text" is a protocol which different systems speak differently.
> It consists of lines of printable characters which are delimited by
> system-specific control characters. A revision control system should use
> whatever notion of "text" the host operating system uses, and translate
> whenever data comes or goes from the system.
>
> So, whats everyone's opinion? I personally prefer #2, since it prevents
> nastiness in my patches, and fixing-line-endings is something that you
> expect to deal with when directly copying between diverse systems. (In an
> implementation, I would expect that all transmission is done using \n, and
> then windows platforms would add \r when applying, and remove it when
> patching) I imagine it would be easy to implement, though it would then
> probably be requested "optional", and then need a default, and
> documentation, and a help entry...
>
> -Mike
#2, Pleeeeease. I don't even care what the default is, if it can be specified
in _darcs/prefs/.
Of course this doesn't apply to any file that matches a pattern in
_darcs/prefs/binaries.
- --
Nigel Rowe
rho@xxxxxxxxxxxxxxx
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFBgeuABbmcM2pfckkRAqwNAJ9AQyaQGPCdmbdOypbzGJl392kEVgCdGtUN
cuDurhRUnYje08nkub85Feo=
=MH/2
-----END PGP SIGNATURE-----
|
