Andreas,
- please read my reply to Mike.
I know of "cvs tag", but
- the problem is the same as with RN (Revision Number): how the find
the repository highest values, 10 times a day/developer.
- it's less convenient to use than RN : while there is a field for
the RN in the commit dialog, there is none for tag.
- We rather see tag as a timestamp for the whole project
"version 1.0, shipped on 14/2/2002".
, not for a few files
"fixed bug 007"
Alain Ravet
Andreas Bielk wrote:
> Exactly. I was going to respond to Alain, but Mike did such a good job.
>
> So I'll only add that what you probably want, Alain, is "cvs tag" and
> it's
> thoroughly explained in the CVS manual.
>
> --andreas
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]] On Behalf Of Mike Lehmann
> Sent: den 22 mars 2002 11:45
> To: [EMAIL PROTECTED]
> Subject: [Eap-features] Re: [Eap-list] CVS how to : new revisionNumber
> <-- MAX( proj
>
>
> Hello Alain,
>
> I'm sure, you never read the CVS manual or you simply do not understand
> it.
>
> 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
>
>> From: Alain Ravet<[EMAIL PROTECTED]>
>> Date: Fri, 22 Mar 2002 09:32:28 +0100
>> To: [EMAIL PROTECTED]
>>
>>
>> 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
>>
>
>
> _______________________________________________
> Eap-features mailing list
> [EMAIL PROTECTED]
> http://www.intellij.com/mailman/listinfo/eap-features
>
>
>
>
> _______________________________________________
> Eap-features mailing list
> [EMAIL PROTECTED]
> http://www.intellij.com/mailman/listinfo/eap-features
>
>
>
_______________________________________________
Eap-features mailing list
[EMAIL PROTECTED]
http://www.intellij.com/mailman/listinfo/eap-features
