Re: Updating revision number on a branch.

[Fabian Cenedese]

>>Heh, I think you misunderstood my second message.  I meant that we
>>wanted to make the change for cosmetic reasons, not that it WAS a
>>cosmetic change.  After reading on how the branches are created, I
>>understand why you don't want to mess with those.  However, I don't
>>understand what the problem is with updating the revision numbers on
>>the main trunk.  Am I seriously missing something because I see people
>>doing this all the time? :)  Or are all these people just treading into
>>dangerous waters?  And yes, we know how to use symbolic tags and have
>>been using them, so the issue isn't that we don't know how to do that.
>>This is just a curiosity thing at this point in time.  
>
>As a general rule, I resist any changes "for cosmetic reasons" to a 
>non-cosmetic process, tool or data.

Another possibility could be to start a new module/repository. Then it's
quite clear where the files come from, even if they only have 1.x revisions.
Of course that needs some work as well, new checkouts...

bye  Fabi