[Seaside-dev] commit messages

[Philippe Marschall]

2011/6/21 Julian Fitzell <jfitzell at gmail.com>:
> Well, ok. I disagree (I'll save the details for some other time :) ), but I
> see the issue change emails too, so as long as you describe what the *fix*
> was in the issue log, that will serve the same purpose.
>
> And please don't be dramatic, Philippe. I'm asking for a phrase - maybe 20
> seconds of your time per commit - to save everybody else following the
> project from having to load an image, wait an eternity for Monticello to
> load the package, and study the diff. How many commits have you done in the
> last month? Are you really telling me 20 seconds for each of those adds up
> to enough "corporation bullshit" to cause the failure of our project? Sorry,
> I don't buy it for a second.

Well how many commits have you done in the last month that I can take
as an example?

> I was simply asking if people writing code would be willing to do me the
> favour of investing a few seconds of their time to make life a little easier
> for people reading it.

It's totally obvious from the change _and_ the issue what the problem
and the fix was. I don't feel the need to repeat myself a third time.
For the longest time we wouldn't even have an issue tracker and let
alone a change log that would list all the issues that we fixed in a
release. I mean seriously now you get all this for free and still
manage to complain? Fuck, I don't even complain about the shitty RB
anymore.

I could also put in static types in the code. I'm sure some people
would argue that is very helpful and would save them some time.

If you have any question about any code or commit feel free to ask and
I'm happy to answer. But even more bureaucratic overhead, no thanks.

Cheers
Philippe