RE: [Gnu-arch-users] Why commits always increase revision?!

[Попков Александр]

Andrei A. Voropaev wrote:
> "Revision" in cvs and "Revision" in gnu arch are completely different
> things. In cvs each "source file" has its own revision. So - no changes
> to sources - no changes to revision. In gnu arch "revision" means a
> state of the whole project tree (you can think of it as of tag in cvs).
> Besides the sources the gnuarch revision keeps trap of "patch log"
> entries (your "test" string). So, when you do commit, you add new patch
> log entry, thus you create new revision. Again you can compare it with
> "tagging" in cvs. The tag will be created independantly from the changes
> in the "sources". (But there'll be no log messages attached to it.)

Thanks! 

So quote from http://wiki.gnuarch.org/Tla_20Reference_2fcommit
---------------------------------------------------------------------------
The usual way to commit: 

$ tla changes
[...]
$ vi `tla make-log`
$ tla commit
(No, tla changes is not mandatory, but highly recommended before committing) 
---------------------------------------------------------------------------
suggest to using `tla changes' before `tla commit' for prevent 'empty' commits? 
Right?