[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: -t/-f in cvswrappers

From: Jerry Nairn
Subject: RE: -t/-f in cvswrappers
Date: Fri, 13 Apr 2001 13:57:38 -0700

>From: DAve Goodrich [mailto:address@hidden
>Sent: Friday, April 13, 2001 12:43 PM

>on 4/13/01 12:26 PM, address@hidden at 
>> the line endings should get translated by the client.  If 
>they are not
>> being translated, then there is a problem with that client.  
>Perhaps it
>> is misconfigured.
>Agreed, the developer know this and is working on it. See above.

I still don't think you understand what's being said. Using Mac line endings
in text on a Mac should be irrelevant. I looked at the MacCVSClient web
site. The product seems very well documented, and there's no mention of any
problem like this. The online user guide indicates this is handled
correctly. It would be surprising if it wasn't.
Something you could be doing which would cause this problem, and no one has
mentioned yet, is checking in text files as binary. Your Mac client happens
to implement several storage formats. If your users choose formats which
don't allow eol conversion, that could cause this problem, among others.

>> All these things can be done using a trigger script placed 
>in the commitinfo
>> file.

>I'll look into that, any examples? I'm not sure how that would 
>work. Would
>this enable a file to be changed? or would it only be able to 
>validate and
>then reject/accept a file for commit based on the result of the regular
>expression. Ideally to solve this problem, I need to filter a 
>file through a
>process between the client and the repository.

You can do this, but you need to look at the manual.
If you have any questions after that, I'm sure there are people here who can

reply via email to

[Prev in Thread] Current Thread [Next in Thread]