Well of course, if you do not commit directories but a few files, then yes, 
you might have a problem.

Otherwise, it means that you have forgotten to add a file. So it will be
? ForgottenFile
for any commit or update.

There is also the particular case when you do not want to commit a new change 
in a file but forgot that without modification of that file you cannot commit 
the other modified files either.

Well, at least, that are the traps where I have fallen at least once.

On Tuesday 18 November 2003 13:55, Melchior FRANZ wrote:
> * Nicolas Goutte -- Tuesday 18 November 2003 13:48:
> > But what brings a cvs up after committing? If the question marks were
> > overseen while committing, they will probably been overseen in an update
> > too.
> >
> > (Also, as one is supposed to make an update before committing, the
> > missing files could have been seen at this moment too.)
>
> Well, before the commit you'll probably see a lot of locally
> modified files. That's why you are committing in the first place.
> "cvs up" is only done here to see if there are conflicts. But
> after committing, if "cvs up" =still= returns locally modified
> files, then you have obviously forgotten something, no?
>
>   $ cvs ci
>   ...
>   $ cvs up
>   M Makefile.am
>
>   Damn ...   :-)
>
> m.
>
> >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to
> >> unsubscribe <<

 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<