Re: [Monotone-devel] line endings and binary files revisited...

2005-05-23 Thread Will Robertson
That's handy to know -- I might need to use my repositories on all 3 of
these platforms, soon.


On Sat, 2005-05-21 at 18:19 -0700, Nathaniel Smith wrote:

[...]

> The current policy is:
>   -- by default, don't touch line endings at all.  In fact, don't
>  touch data at all, we store uninterpreted bytestreams.
>   -- if the user requests, they can have line endings converted one
>  way going out of their working copy, and back again when going
>  into their working copy.  I don't know if there's a way to make
>  this apply only to specific files, though.
> 
> -- Nathaniel
> 



___
Monotone-devel mailing list
Monotone-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/monotone-devel


Re: [Monotone-devel] line endings and binary files revisited...

2005-05-22 Thread Richard Levitte - VMS Whacker
In message <[EMAIL PROTECTED]> on Sat, 21 May 2005 18:19:36 -0700, Nathaniel 
Smith <[EMAIL PROTECTED]> said:

njs> The current policy is:
njs>   -- by default, don't touch line endings at all.  In fact, don't
njs>  touch data at all, we store uninterpreted bytestreams.

Oh, I guess I had misunderstood it...

njs>   -- if the user requests, they can have line endings converted one
njs>  way going out of their working copy, and back again when going
njs>  into their working copy.  I don't know if there's a way to make
njs>  this apply only to specific files, though.

Thanks for clarifying.

-
Please consider sponsoring my work on free software.
See http://www.free.lp.se/sponsoring.html for details.

-- 
Richard Levitte [EMAIL PROTECTED]
http://richard.levitte.org/

"When I became a man I put away childish things, including
 the fear of childishness and the desire to be very grown up."
-- C.S. Lewis


___
Monotone-devel mailing list
Monotone-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/monotone-devel


Re: [Monotone-devel] line endings and binary files revisited...

2005-05-21 Thread Nathaniel Smith
On Sun, May 22, 2005 at 01:56:35AM +0200, Richard Levitte - VMS Whacker wrote:
> I have the feeling that however good, there's always a possibility
> that a non-text files be interpreted as text files.  As long as you're
> playing entirely in Unix, it's not a problem, since the line ending is
> a \n, so there will be no conversion.  On Windows or on Mac, where the
> line endine is \r\n and \r respectively, the matter is different.
> 
> I'm thinking that files should be stored entirely unchanged in the
> database, and *possibly* be interpreted on output.  It has the benefit
> of not being destructive, which I think would be a good thing...

The current policy is:
  -- by default, don't touch line endings at all.  In fact, don't
 touch data at all, we store uninterpreted bytestreams.
  -- if the user requests, they can have line endings converted one
 way going out of their working copy, and back again when going
 into their working copy.  I don't know if there's a way to make
 this apply only to specific files, though.

-- Nathaniel

-- 
Eternity is very long, especially towards the end.
  -- Woody Allen


___
Monotone-devel mailing list
Monotone-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/monotone-devel


[Monotone-devel] line endings and binary files revisited...

2005-05-21 Thread Richard Levitte - VMS Whacker
Hi,

More than half a year ago, we had a discussion about how line endings
should be treated when storing files in the database, and how
differentiation between non-text (binary) and text files should be
performed.

I don't recall what the concensus was, except that line endings are
converted to \n before storing the file in the data base.

I have the feeling that however good, there's always a possibility
that a non-text files be interpreted as text files.  As long as you're
playing entirely in Unix, it's not a problem, since the line ending is
a \n, so there will be no conversion.  On Windows or on Mac, where the
line endine is \r\n and \r respectively, the matter is different.

I'm thinking that files should be stored entirely unchanged in the
database, and *possibly* be interpreted on output.  It has the benefit
of not being destructive, which I think would be a good thing...

Comments?

Cheers,
Richard

-
Please consider sponsoring my work on free software.
See http://www.free.lp.se/sponsoring.html for details.

-- 
Richard Levitte [EMAIL PROTECTED]
http://richard.levitte.org/

"When I became a man I put away childish things, including
 the fear of childishness and the desire to be very grown up."
-- C.S. Lewis


___
Monotone-devel mailing list
Monotone-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/monotone-devel