|}avid writes: > > cvs history blah.c > > spits out HUGE amounts of info on millions of files, not just on blah.c as I > would expect. Therefore in 'cvs history [options] files...' 'files....' > doesn't refer tot he same thing it does in other commands. Yes it does. The confusion is that history, by default, produces a report of checked-out *modules*, so the file name is ignored. If you specified a type of report that applies to files (e.g., -c), it would work as you expect. -Larry Jones Ever notice how tense grown-ups get when they're recreating? -- Calvin
- Re: CVS File Locking Win32 M$
- Re: CVS File Locking Tobias Weingartner
- Re: CVS File Locking Paul Sander
- RE: CVS File Locking Chris Cameron
- Re: CVS File Locking Noel L Yap
- Re: CVS File Locking Noel L Yap
- cvs history command? |}avid (opeland
- Re: cvs history command? Greg W. Moore
- Re: cvs history command? |}avid (opeland
- Re: cvs history command? Greg W. Moore
- Re: CVS File Locking Larry Jones
- Re: CVS File Locking Win32 M$
- Re: CVS File Locking Paul Sander
- Re: CVS File Locking Greg A. Woods
- Re: CVS File Locking Paul Sander
- Re: CVS File Locking Greg A. Woods
- Re: CVS File Locking Paul Sander
- Re: CVS File Locking John Macdonald
- Re: CVS File Locking Noel L Yap
- Re: CVS File Locking Noel L Yap
- Re: CVS File Locking Paul Sander
