RevisionLinkPlugin used non API calls in Cairo (it could actually have been implemented with API - all it needed was there).
Plugin is being updated to work with both Dakar and Cairo.
During the updating I found other bugs so I rewrote the entire plugin (and learned some perl in the process
As I write this report all is ready for checking in.
KJL
I have now checked it in. I need some help. In the change history I want the SVN number as a static number.
I want 18 May 2006 (2.0 - SVN 10227) instead of 18 May 2006 (2.0 - SVN $Rev: 10227 $)
CC how the heck do you do that in your plugins? Do you check the latest SVN number and then hurry up committing hoping that noone does it 2 seconds before you?
The use of $Rev$ or whatever you use should be added to the developer docs. I cannot find anything about it on TWiki.org
KJL
By advice from Peter I used the
hurry and hope method.
Ie.
- Look at the latest SVN number.
- Hurry updating the topic and commit it.
- Hope that noone else committed anything just before you.
If there is a better way please add it to the docs in TWiki.org
KJL
Fixing cosmetics on plugin topic. Will not bump revision. Just doing it now on SVN so I won't forget.
KJL