Skip to main content ↑ ↓
Topic: Board Mascot. (Read 8182 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Board Mascot.

'Nuff said.
The best moment for testing your PR is right after you merge it. Can't miss with that one.

Re: Board Mascot.

Reply #1 –

Are you saying we needs more features  8)

Re: Board Mascot.

Reply #2 –

I plead innocent on that. (you know it's all my fault anyway, but these are details)

 TestMonkey suspects on the other hand, that Spuds has set the github issues tracker with only 'enhancements' label, and no 'feature requests', with the dark purpose to call 'em enhancements and add MOAR that way...
The best moment for testing your PR is right after you merge it. Can't miss with that one.

Re: Board Mascot.

Reply #3 –

TestMonkey wants to apply Moores Law to software  ....  the number of features will double approximately every two years while the number of lines of code will quadruple  :P

Re: Board Mascot.

Reply #4 –

 emanuele is thinking of adding a cool thing to the link tree: have you seen how nowadays file manages handle these things? O:) (that would make the "jump to" completely useless)

ETA: even though I have no clear idea how to realize it. :P
Last Edit: December 09, 2012, 06:08:35 am by emanuele
Bugs creator.
Features destroyer.
Template killer.

Re: Board Mascot.

Reply #5 –

We need this girl for project mascot.

Master of Expletives: Now with improved family f@&king friendliness! :D

Sources code: making easy front end changes difficult since 1873. :P