[Top][All Lists]

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

Re: -t/-f in cvswrappers

From: Rex_Jolliff
Subject: Re: -t/-f in cvswrappers
Date: Fri, 13 Apr 2001 12:26:47 -0700

DAve Goodrich <address@hidden> on 04/13/2001 12:03:25 PM

 To:       Larry Jones <address@hidden>                 
 cc:       address@hidden(bcc: Rex Jolliff/YM/RWDOE)        
 Subject:  Re: -t/-f in cvswrappers                           

                                            Federal Record Status Not Determined

>on 4/12/01 4:36 PM, Larry Jones at address@hidden wrote:
>> DAve Goodrich writes:
>>> Hello all. I'm running into a problem with clients that send files to the
>>> repository with Mac or Win file endings.
>> What clients are these?  It is the client's responsibility to convert
>> text files from whatever the local line ending convention is to the
>> canonical line-feed termination before sending them to the server.  If
>> that isn't happening, the clients are buggy or misconfigured.

> We have several people using MacCVSClient, which uses Mac line endings by
> default. The developer knows that people who are creating code that must
> eventually live on a Unix box(web pages) have a problem with this (me) and
> he is working to remedy that.

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.

>> You
>> aren't using some kind of shared file system and trying to commit files
>> from a different platform than the one you're running on, are you?

> Nope creating web pages on Mac/Windows and serving from Unix.

I do not think you understood his question.  Are you using the pserver
method, the rsh/ssh method or a shared drive to access the cvs
repository.  If you are using a shared drive, then this is your

>>> But I get an error that "cvs [server aborted]: -t/-f wrappers not supported
>>> by this version of CVS"
>> There were bugs in the -t/-f wrapper code that could cause silent loss

> Thanks, not what I wanted to hear, but oh well.

>Seems that would be an extremely useful function. I would like to be able to
>filter many things through a file prior to committing, check for common
>copyright code at the bottom of a file, check for tags ($RCSfile$) at the
>beginning of each file, things I must do weekly in code review. Odd it seems
>to have been forgotten so long.

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


reply via email to

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