Mike
1� Thanks for the nice words.
Mike Lehmann wrote:
> I'm sure, you never read the CVS manual or you simply do not
understand it.
Please read further.
2� I'm sure you never read my mail completely or you simply do not
understand it.
Please, try again and understand my point, and our way of using CVS.
As there are many ways to skin a cat, there is more than 1 way to use CVS.
- In the local/default - your - way, you don't specify a R.N. (revision
number), and CVS will add 1 individually to each file RN.
- In the global way - our way -, RNs are global.
If fixing but007 required modifying
- 3 java files,
- 1 html templates, and
- 1 exel file, where we record progress,
we will commit all those files with
- a common commit message "Fixed bug 007", and
- a common RN : 1.78
Disadvantages :
- you have to specify the RN manually, and make sure it's coherent
with your colleagues actions.
(hence my request to have IDEA find this number for us).
Advantages :
- the RN can be used as a link to logical actions
RN 1.78 <==> "all the changes to fix bug 007"
So, what is so wrong with our way?
Doesn't it make sense?
Alain Ravet
> Each file has it's own revision, you do not need to give all your
file you want to commit one special revision. In 99,99% of the cases you
need not to bother with any revision at all -- only if you want to *get*
(aka "update") a special revision. In general, the option "Commit to
revision" makes really less sense. It just could be useful to put all of
your files to revision 2.0 or 3.0 because your product has the version
2.0 or 3.0. But the cvs manual discourages you to do this.
>
> Mike
>
>
>
>>Subject: [Eap-features] Re: [Eap-list] CVS how to : new
revisionNumber <-- MAX( proj
>>
>> Ian Pojman wrote :
>> >> This makes no sense.. CVS does this automatically and internally.
>> >> when your developers commit or merge, it handles this stuff
internally
>>
>>
>>Wrong. It makes a lot of sense :
>>
>>If you have 4 files, at revision 1.12 level,
>>- you can commit the first 2 to revision 1.29,
>>and then
>>- commit the other 2 to revision 1.13.
>>
>>As we practice micro-commit, we commit 10+ times a day, on average,
between 1 and 10 files.
>>Although we are in the same office, it would make our life easier
that it is now : we write down the number of the latest revision in a
common place, but sometimes we forget..
>>
>>Alain Ravet
>>
>>Alain Ravet wrote:
>>
>>>Request :
>>>*********
>>>In the CVS dialog, next to the [Revision number]field,
>>>Please add a smart (see below) "Increment revision number" button.
>>>
>>>It would be smart (not simply adding 1), by first finding in the CVS
>>>repository the highest revision number, and adding 1 to it.
>>>A little like using MAX (id) +1) to generate an new primary key.
_______________________________________________
Eap-features mailing list
[EMAIL PROTECTED]
http://www.intellij.com/mailman/listinfo/eap-features
