Hi all,

some more or less important news for the developers and users of the CVS. I made a small mistake during commits in the CVS. I used

cvs checkout -r openca_0_9_1

and after this I entered the following for commiting

cvs commit -r openca_0_9_1 xyz

The result is that the actual branch is not updated. The CVS creates a new branch and moves the symbolic name. Now I use commit without -r. So this should never happen again.

Example:

cvs checkout -r openca_0_9_1 openca-0.9

result: xyz with revision 1.10.0.1

mistake: cvs commit -r openca_0_9_1 xyz
result: xyz with revision 1.10.2.1

correct: cvs commit xyz
result: xyz with revisin 1.10.0.2

Today there are two relevant branches:
1. the HEAD branch
2. openca_0_9_1 (this is the branch which includes the most actual changes for the 0.9.1 release - actually only a fix for SPKAC-requests which is not par of the initial 0.9.1)

There are two relevant symbolic tags:
1. openca_0_9_1_RC7
2. openca_0_9_1_0 (the first release of openca-0.9.1)

You can checkout the actual release via

cvs checkout -P -r openca_0_9_1_0 openca-0.9

and the most actual version of 0.9.1 you can get via

cvs checkout -P -r openca_0_9_1 openca-0.9

I hope this helps a little bit and avoid some confusions with the branches.

Michael
--
-------------------------------------------------------------------
Michael Bell Email (private): [EMAIL PROTECTED]
Rechenzentrum - Datacenter Email: [EMAIL PROTECTED]
Humboldt-University of Berlin Tel.: +49 (0)30-2093 2482
Unter den Linden 6 Fax: +49 (0)30-2093 2959
10099 Berlin
Germany http://www.openca.org



-------------------------------------------------------
This SF.NET email is sponsored by: Take your first step towards giving your online business a competitive advantage. Test-drive a Thawte SSL certificate - our easy online guide will show you how. Click here to get started: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0027en
_______________________________________________
OpenCA-Devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/openca-devel

Reply via email to