bug-cvs
[Top][All Lists]
Advanced

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

Re: Commit problem


From: Paul Edwards
Subject: Re: Commit problem
Date: Thu, 25 Dec 2003 04:43:32 GMT

"Nick" <saber850@yahoo.com> wrote in message 
pan.2003.12.24.21.26.40.38928@yahoo.com">news:pan.2003.12.24.21.26.40.38928@yahoo.com...
> Here's more info regarding this problem.
>
> 1.  As with 'cvs diff', 'cvs update -d' properly determines all files that
> have changed locally.
>
> 2.  If I manually command a commit of the files that changed, only the
> top-most files that changed (w/ respect to dir tree) get picked up.
>
> For example, using this simple tree (again omitting the 'CVS' directories):
> a
> |-- a.txt
> `-- b
>     |-- b.txt
>     `-- c
>         `-- c.txt
>
> where I modified all TXT files.  My pwd is a/
>
> 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).

You're talking about the changelog editor?  No idea about
that.  What happens if you use the command line and do
a cvs commit -m "blah blah blah" a.txt b/b.txt etc.

If that works fine, then maybe the changelog editor is not
working in your preferred manner.  Commit probably
works fine though.

BFN.  Paul.




reply via email to

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