Boost logo

Boost :

From: Miro Jurisic (macdev_at_[hidden])
Date: 2004-04-12 12:44:47


In article <BC9F3B11.91AE%darylew_at_[hidden]>,
 Daryle Walker <darylew_at_[hidden]> wrote:

> On 4/9/04 7:34 PM, "Miro Jurisic" <macdev_at_[hidden]> wrote:
>
> > FWIW, CVS regulates (inasmuch as CVS regulates anything) that the client
> > canonicalize text files before sending them, and the server sends the files
> > to the client in a canonical form, as you thought.
>
> So, the initial CVS client has to convert the text file to UNIX format? And
> the server won't sanity-check this in either direction, which means a later
> client will apply the UNIX-to-native translation on a file that may not be in
> the UNIX format?

I am not sure how you think you got into this state; if all clients perform
newline conversion and the server is not buggy then the client will never
perform UNIX-to-native conversion on a file that doesn't have UNIX newlines.

> The system would only work right if the uploading and downloading clients
> both correctly do UNIX translation

Yes, the system does depend on that.

meeroh

-- 
If this message helped you, consider buying an item
from my wish list: <http://web.meeroh.org/wishlist>

Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk