Mailing list etiquette

Adrian Buehlmann adrian at cadifra.com
Sat Sep 8 04:55:27 CDT 2012


On 2012-09-07 19:42, Bryan O'Sullivan wrote:
> In isolation, calling something "broken" is not impolite. But I see
> enough mail where the tone is aggressive or unpleasant that it has me
> perpetually on my guard; that's the bigger issue. If this was just an
> isolated use of one phrase, I wouldn't be calling attention to it.

Of course you are free to judge yourself whether you find my tone
aggressive or not.

I don't think I'm aggressive, nor do I think I have a general problem in
that regard.

I saved your but by catching some severe bugs in big pile of almost
indigestible C code by adding some thoughtful tests and I didn't
applaud, yes.

Apparently you are angry and can't stand my critique.

You are not an infallible pope. If you send a patch to this list then
you can expect that I speak up. I'm not afraid of doing it, I don't care
what reputation you hold.

No one (except Matts and myself so far) had the guts to dissect and
critically comment on your C patches so far. And it seems Matt agrees
with me on splitting the fncache patch up and keeping the hashed paths
code path in Python in a first step:

http://selenic.com/pipermail/mercurial-devel/2012-September/044098.html

Resorting to public personal attacks by publicly calling me an arse IMHO
rather reflects badly on yourself, especially if you do that in a public
email with the subject "Mailing list etiquette".

Calling me an arse is in my view rather an indication that it's *you*
who have a problem with the "Mailing list etiquette".


More information about the Mercurial-devel mailing list