It's easy to overlook. It isn't the file that dictates the revision ID. It's the module; from the manual ...
"When adding a new file, the second number will always be one and the first number will equal the highest first number of any file in that directory. For example, the current directory contains files whose highest numbered revisions are 1.7, 3.1, and 4.12, then an added file will be given the numeric revision 4.1." Regards, Mike Klinke On Wednesday 05 March 2003 19:58, Todd A. Jacobs wrote: > > By definition, a new file in a module does not *have* a previous > revision, so this would not be relevent. Since revision numbers are > assigned per-file and not per-module, revision numbers of other files > in the module should have no effect. -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
