[Top][All Lists]

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

Re: CVS diff and unknown files.

From: Mark D. Baushke
Subject: Re: CVS diff and unknown files.
Date: Sat, 22 Jan 2005 18:59:33 -0800

Hash: SHA1

Hi Greg,

Greg A. Woods <address@hidden> writes:

> [ On , January 21, 2005 at 20:06:37 (+0300), address@hidden wrote: ]
> > Subject: CVS diff and unknown files.
> >
> > Is there a way to include contents of "unknown" files into the 'cvs
> > diff' output?
> > 
> > I did try the -N switch but it doesn't seem to do the trick.
> You must "cvs add" the files before they can be seen as new.
> > I can't 'cvs add' the files as the repository is read-only for me
> > (public read-only repository of an open-source project).
> Yes, you can, or at least you should be able to.
> "cvs add" does not (and must not :-) contact the server.

When I use

    mkdir foo
    cvs add foo

it contacts the server and creates the directory on the remote
reposiotry using either the current stable or feature releases of CVS.

In addition, I believe you will find that a 'cvs add' for a normal file
will also contact the server in order to create a CVS/Entries entry for
the new file with a '0' version and a 'dummy timestamp' as well.

While it has been proposed that this behavior should be changed, no
change to this behavior has been committed to the CVS sources as yet.

So, even if it 'must not' exhibit this behavior, it does appear to
exhibit it at present.

        -- Mark
Version: GnuPG v1.2.3 (FreeBSD)


reply via email to

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