[Top][All Lists]

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

Re: Commit problem

From: Nick
Subject: Re: Commit problem
Date: Fri, 26 Dec 2003 18:52:54 GMT
User-agent: Pan/0.13.96 (You appear to be in death, comrade.)

> The change log editor is invoked
> once per directory, not once per commit.
Ok, now I'm lost.  I setup a simple repository at work as mentioned in a
previous post (a/b/c dirs).  When I commit from the top-level dir, it
yields the same results at home--the editor prompts for a description for
each directory.
But, if I commit on my other repository (the one that has been running for
~6 months), the editor only asks for one change log and lists all
files--including those in subdirs.  It also commits all the files that
changed (including those in different dirs) using the specified change log
(ie. only asks me once).

Larry, you say this is normal for CVS.  But for all that I've used CVS, it
only prompted me for one change log entry and applied it to all files that
changed (including those in subdirs).  The behavior is certainly
different, else I wouldn't be posting about it.

Is there an option to control this behavior?  


On Thu, 25 Dec 2003 16:00:32 -0500, Larry Jones wrote:

> Nick writes:
>> If I try 'cvs commit a.txt b/b.txt b/c/c.txt' only a.txt is reported in the
>> Change Log editor (b.txt and c.txt are ignored).
>> If I try 'cvs commit b/' only b.txt is acknowledged (c.txt is ignored).
> That's exactly what should happen.  The change log editor is invoked
> once per directory, not once per commit.
> -Larry Jones
> At times like these, all Mom can think of is how long she was in
> labor with me. -- Calvin

reply via email to

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