[Top][All Lists]

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

Re: Ignoring whitespace and CR/LF when checking into repository

From: Antony Paul
Subject: Re: Ignoring whitespace and CR/LF when checking into repository
Date: Sat, 20 Nov 2004 14:32:14 +0530

What I mean by a server is something like pserver. My understanding
about CVS is that it requires client only(downloaded from
) to create a repository and do checkout and checkin. I tried this in
    The repository that created this problem have no server running.

Antony Paul 

On Fri, 19 Nov 2004 08:55:43 -0800, Mark D. Baushke <address@hidden> wrote:
> Hash: SHA1
> Antony Paul <address@hidden> writes:
> > Does making files binary using -kb compromises any other
> > functionality. Some developers want CVS to merge changes
> > automatically. If the file is treated as binary will it merge ?.
> No.
> > Does any one have an example of a commitinfo filter which can identify
> > ASCII files ?
> That depends on what you mean... the commitinfo script could look at the
> output of `cvs -n status filename` to see if the user has specified -kb
> or not.
> It might also be possible to use the output of `file filename` on *NIX
> servers for new files that are being added to see if the user is doing
> something unexpected. Of, you could write your own custom tool that
> looked at the file, but do understand that the file copy on the server
> side may already have been 'corrupted' in transit if the -kb switch was
> not specified in the first place and the file really was a binary that
> the client is not properly treating as a binary.
> > Using commitinfo does requires a server ?.
> The commitinfo trigger is run on the server.
>         -- Mark
> Version: GnuPG v1.2.3 (FreeBSD)
> iD8DBQFBniWO3x41pRYZE/gRAh0RAKC65AzFeBAlSbbEFisr2fx3dVGLSgCgs9qL
> zi/DFkjsCkZVxbuBWkTLSRQ=
> =GuRj

reply via email to

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