From: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
To: David Allsopp <dra-news@metastack.com>
Cc: "Adrien Nader" <adrien@notk.org>,
"Malcolm Matalka" <mmatalka@gmail.com>,
"caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] Suggested way to determine platform specific capabilities in build system?
Date: Sun, 19 Apr 2015 14:11:48 +0200 [thread overview]
Message-ID: <1C4B8D903341432CB5D1CAF025C3814F@erratique.ch> (raw)
In-Reply-To: <E51C5B015DBD1348A1D85763337FB6D9E9A8A570@Remus.metastack.local>
Le dimanche, 19 avril 2015 à 12:13, David Allsopp a écrit :
> > I know this is the way autocrap likes to work; it may seem smart but I
> > think that's completely retarded.
>
> Um, while your arguments often veer a little towards ad hominem attacks, the word "retarded" used in this context is extremely offensive, even if that is not what you intended (making allowance that while your English is extremely good, it is not your first language).
I don't see any ad hominem attack here I'm criticizing tools and approaches — if Adrien think there is one, I'm sorry and tell him he should not take it as such.
Regarding the sentence you mention I'll rephrase it just for you (or any other person I may have offended):
❀ I know this is the way autoheaven likes to work, however it seems that while I can appreciate that this technique has his merits I do have slight concerns with it. ❀
Best,
Daniel
next prev parent reply other threads:[~2015-04-19 12:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-14 10:51 Malcolm Matalka
2015-04-14 11:23 ` Daniel Bünzli
2015-04-14 13:17 ` Thomas Gazagnaire
2015-04-19 6:47 ` Adrien Nader
2015-04-19 8:38 ` Daniel Bünzli
2015-04-19 10:13 ` David Allsopp
2015-04-19 12:11 ` Daniel Bünzli [this message]
2015-04-19 19:14 ` Emmanuel Surleau
2015-04-20 9:55 ` Ben Millwood
2015-04-17 10:38 ` Ivan Gotovchits
2015-04-21 21:36 ` Richard W.M. Jones
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1C4B8D903341432CB5D1CAF025C3814F@erratique.ch \
--to=daniel.buenzli@erratique.ch \
--cc=adrien@notk.org \
--cc=caml-list@inria.fr \
--cc=dra-news@metastack.com \
--cc=mmatalka@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).