gnu-arch-users
[Top][All Lists]
Advanced

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

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


From: Попков Александр
Subject: [Gnu-arch-users] Why commits always increase revision?!
Date: Tue, 15 Mar 2005 13:22:19 +0300

Hello GNU ARCH users!

 

I am having a little question: why commits always increase revision?!

 

address@hidden project]$ tla import --setup

* creating category address@hidden/znak

* creating branch address@hidden/znak--stable

* creating version address@hidden/znak--stable--1.0

* imported address@hidden/znak--stable--1.0

address@hidden project]$ tla logs

base-0

address@hidden project]$ tla changes

* looking for address@hidden/znak--stable--1.0--base-0 to compare with

* comparing to address@hidden/znak--stable--1.0--base-0

address@hidden project]$ tla commit -L "test"

* update pristine tree (address@hidden/znak--stable--1.0--base-0 => znak--stable--1.0--patch-1)

* committed address@hidden/znak--stable--1.0--patch-1

address@hidden project]$ tla changes

* looking for address@hidden/znak--stable--1.0--patch-1 to compare with

* comparing to address@hidden/znak--stable--1.0--patch-1

address@hidden project]$ tla commit -L "test"

* update pristine tree (address@hidden/znak--stable--1.0--patch-1 => znak--stable--1.0--patch-2)

* committed address@hidden/znak--stable--1.0--patch-2

address@hidden project]$ tla changes

* looking for address@hidden/znak--stable--1.0--patch-2 to compare with

* comparing to address@hidden/znak--stable--1.0--patch-2

address@hidden project]$ tla commit -L "test"

* update pristine tree (address@hidden/znak--stable--1.0--patch-2 => znak--stable--1.0--patch-3)

* committed address@hidden/znak--stable--1.0--patch-3

address@hidden project]$ tla changes

* looking for address@hidden/znak--stable--1.0--patch-3 to compare with

* comparing to address@hidden/znak--stable--1.0--patch-3

address@hidden project]$ tla commit -L "test"

* update pristine tree (address@hidden/znak--stable--1.0--patch-3 => znak--stable--1.0--patch-4)

* committed address@hidden/znak--stable--1.0--patch-4

address@hidden project]$ tla changes

* looking for address@hidden/znak--stable--1.0--patch-4 to compare with

* comparing to address@hidden/znak--stable--1.0--patch-4

address@hidden project]$ tla commit -L "test"

* update pristine tree (address@hidden/znak--stable--1.0--patch-4 => znak--stable--1.0--patch-5)

* committed address@hidden/znak--stable--1.0--patch-5

address@hidden project]$ tla revisions --summary

base-0

    initial import

patch-1

    test

patch-2

    test

patch-3

    test

patch-4

    test

patch-5

    test

 

In CVS ‘commit’ don’t touch repository unless some files have changes, and I am think this is right.


reply via email to

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