Every morning before any of the meetings get started I print out a small one page newsletter which contains (among other things) the program for the day. Rather than keep them private, Colin suggested I post them here. I call the newsletter the “MariaDB Programador de Journal” which (I think) translates to “MariaDB Programmer’s Journal” in Portuguese.
[Updated, 13 Mar 2011, to add the newsletter for that day.]
At the meeting we’ve also been taking notes and posting them online for what improvements we want to make this year in MariaDB to make it even better. You can find the notes in the Knowledgebase. If you have any suggestions for things you would like to see in the next version of MariaDB, please leave a comment in the Knowledgebase.
We want MariaDB to always be the best version of MySQL available anywhere, and letting us know what you need and new features that you like to have is an important part of the process.
The developer meeting in Lisbon, Portugal is about to start, and there’s an agenda available. If you’re not going to be in Lisbon, please hop onto IRC and join the #maria channel on Saturday March 12 2011 (UTC+0) as the roadmap for MariaDB is to be discussed live as well as via IRC.
If you have further agenda items and cannot make it to Lisbon, use the mailing list: email@example.com – make sure you’re subscribed.
I don’t know about you, but I like diff -p . Having used it for years, I can read these diffs like a text, while diffs without -p often need to have the original file opened side by side, just to get enough of the context.
Loving diff -p so much, I want to see it everywhere (evil laughter). Alas, in bzr only diff command can easily use -p, just run it as bzr diff --diff-options=-p or store it as an alias in the ~/.bazaar/bazaar.conf.
Actually, for an alias there is a better, although more verbose, alternative:
Unlike simple -p it will not think that a word ending with a semicolon (like a label or, say, public: and private:) is a “C function name”.
But the problem is — only bzr diff can be tuned this way. Bzr email plugin still sends diffs without function names. And bzr gdiff does not show them. And, of course, all other bzr commands — bzr commit, for example, or bzr shelve, bzr unshelve --preview, bzr log --show-diff and others — they are still as unfriendly as before.
I was solving it on a case by case basis — added a post_commit_diffoptions configuration option to the bzr-email plugin, then a command line option to bzr gdiff. But then it occurred to me that I can attack the problem at its core! Continue reading →