[Top][All Lists]

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

RE: CVS asking for one log message per directory with file changes

From: Jeff Pream
Subject: RE: CVS asking for one log message per directory with file changes
Date: Thu, 18 Jan 2007 09:26:32 -0800

Adding :fork: to the CVSROOT took care of the issue.

All of our work is behind the corporate firewall, but I'll make sure IT
gets a notice of the security hole and they can choose to install

Thanks again.


-----Original Message-----
From: address@hidden [mailto:address@hidden On Behalf Of Mark D.
Sent: Thursday, January 18, 2007 9:21 AM
To: Jeff Pream
Cc: address@hidden
Subject: Re: CVS asking for one log message per directory with file

Hash: SHA1

Hi Jeff,

You may wish to use the :fork:/path/to/repository method for your
CVSROOT instead of just /path/to/repository as this will prompt you for
a single log message for the entire commit.

Be advised that cvs 1.12.13 came out because of a security problem in
1.12.12 in the zlib compression library...

See for details.

        -- Mark

Jeff Pream <address@hidden> writes:

> All,
> Using cvs 1.12.12 I have created a repository in my home directory so
> that I can work on some trigger script issues while not messing with a
> project repository.   With the local repository, when I commit changes
> from multiple directories, CVS sequentially asks (pops open vi) for a
> log message for each directory that had file changes.
> Is there something I need to do to get CVS to commit all changes
> regardless of directory using one message entered from an editor?
> I have never seen this before, but I've only used pserver
> before this (if that should make any difference).  This behavior is
> blocking an issue I was seeing in our project repository (also using
> 1.12.12) which I will probably post about separately.
> Thanks in advance for your help.
> Jeff
> _______________________________________________
> info-cvs mailing list
> address@hidden
Version: GnuPG v1.4.6 (FreeBSD)


reply via email to

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