From: Bastien <bzg@gnu.org>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH] ox.el: Fix extra character deleted in org-export--update-included-link
Date: Thu, 13 Feb 2020 12:01:23 +0100 [thread overview]
Message-ID: <878sl6px8c.fsf@bzg.fr> (raw)
In-Reply-To: 87wo8qvl5x.fsf@nicolasgoaziou.fr
Hi Nicolas,
I'm glad I replied to your email because...
Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> Last time we disagreed, you grossly concluded with:
>
> Future maintainers may of course interpret the recommendations of the
> FSF differently, but that's mine for now.
>
> As far as my understanding permits, this means: "I'm am the one in
> charge. I know what I'm doing. Discussion closed. Next."
... we are clearly miscommunicating here.
When I said:
Future maintainers may of course interpret the recommendations of
the FSF differently, but that's mine for now.
I just really meant what I said: future maintainer(s) can decide what
is the best interpretation of "15 lines of (significant) changes", but
since I'm the one responsible for handling copyright stuff for Org, I
ask you and co-maintainers to act as if my interpretation were true.
I didn't even imagine my statement could be rude, but I know see how
it can be perceived as rude, given the context. Sorry for that.
> I find this stance dubious, whatever the subject is, or if you are right
> or wrong. To make my point go through, I'm now pushing it up to the
> absurd. My intent is to warn, not to hurt.
It did hurt, as sarcasm always does somehow.
> I also believe that lecturing others about communication on mailing
> lists, or social behaviour in general, is not helpful either. Unless, of
> course, you think being patronizing is more acceptable here than being
> ironic. I hope you don't.
I don't.
I did not want to "lecture" or to "patronize", but I wanted to express
my feelings and listen to what I may have done wrong.
On a more general topic, I hope you don't disagree with the addition
of the GNU kind communication guidelines that I recently mentioned in
the manual.
--
Bastien
next prev parent reply other threads:[~2020-02-13 11:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-03 13:14 [PATCH] ox.el: Fix extra character deleted in org-export--update-included-link Christoffer Stjernlöf
2020-02-11 15:55 ` Bastien
2020-02-11 18:15 ` Nicolas Goaziou
2020-02-13 8:12 ` Bastien
2020-02-13 10:25 ` Nicolas Goaziou
2020-02-13 11:01 ` Bastien [this message]
2020-02-13 19:07 ` Adam Porter
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878sl6px8c.fsf@bzg.fr \
--to=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).