10.03.07
cvs commit flashblock/README flashblock/content/flashblock.css flashblock/content/flashblock.xml
Recently, some people have apparently grown tired of checking in the increasingly-large number of patches I’ve been generating. After a little bit of pushing from Sam, I finally filed a bug requesting cvs write access to the mozilla.org source repository, attached the supporting documents and whatnot, and ended up with approval to check in code. (Write access and approval to check in code to a source code repository is a major rite of passage in modern open-source projects.) Being somewhat exhausted last night, I followed good check-in practices and abstained from committing any patches. 
This afternoon, however, I landed the patch to upgrade the Flash-blocking code in Camino to the latest stable version of Flashblock. In fact, I landed the code on the trunk, the MOZILLA_1_8_BRANCH for Camino 1.6a1, and the CAMINO_1_5_BRANCH for Camino 1.5.2, for the vaunted (and somewhat cumbersome) “triple.”
To follow-up on that (and fix a bug that’s annoyed me for quite some time), I landed R P Mozley’s patch for bug 287709, giving our toolbar progress spinner (née throbber) an obvious inactive state on the trunk and the MOZILLA_1_8_BRANCH.
And the tree’s still green (actually, I turned the tree red for the first time a long time ago); here’s to it staying green for years to come!
4 Comments »
Atom feed for comments on this post · TrackBack URL
10.04.07 at 1:55 am
Barman ! A glass of red wine for the gentleman.
10.05.07 at 12:08 am
Thank you, good sir!
I’m wishing I had your internet connection, though; checking in BWC or MainController.mm on DSL can still be a bit scary.
10.05.07 at 6:53 am
Congratulations on commit access Smokey!
01.01.08 at 4:21 pm
[...] to the relief of Stuart Morgan, Ian Leue, and Mark Mentovai, I obtained cvs access in October. I can now check in my own (slowly rising number of) patches, as well as those patches [...]