[Top][All Lists]

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

Re: Preview before commit

From: Mark E. Hamilton
Subject: Re: Preview before commit
Date: Wed, 09 Nov 2005 16:23:43 -0700
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040913

Vikrama Ditya wrote:
I meant cvs commit -n

Well, then, of course it committed that files; you told it to.

'cvs -n commit' is a noop; It does not, as you pointed out, give a list of the files, since id doesn't really do anything.

'cvs commit -n' commits the files without running a tag program. See the description of the common -n option in this section:

Vikrama Ditya also wrote:
> cvs update will also give the list of changes applies from repository to
> local working directory. I am more interested in what goes from working
> directory into reporsitory.

Well, that's true, but you usually don't want to commit until your project up-to-date with what is in the repository and you've run your regression tests. Usually I do two updates in a project; one to merge in all the repository changes, and then one to see a clean list of what would be committed.

Mark E. Hamilton
Orion International Technologies, Inc.
Sandia National Laboratory, NM.

reply via email to

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