From: Catonano <catonano@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel <guix-devel@gnu.org>, Joshua Branson <jbranso@fastmail.com>
Subject: Re: my latest blog post
Date: Sat, 9 Jun 2018 15:07:17 +0200 [thread overview]
Message-ID: <CAJ98PDyquE9PLTVTixyZ7vJ957NPkU_KDEwYkcfEmTObm+0sCA@mail.gmail.com> (raw)
In-Reply-To: <877en8171p.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 2894 bytes --]
2018-06-09 14:24 GMT+02:00 Ricardo Wurmus <rekado@elephly.net>:
>
> Catonano <catonano@gmail.com> writes:
>
> >> Andy’s time is still limited. What other people can do is discuss
> >> *specific* cases on guile-devel and work towards a solution. But please
> >> do not demand of others to explain everything in detail. (I’m directing
> >> this at everyone who heeds my advice to go to guile-devel, not at any
> >> one person in particular.) In order to have a positive impact you also
> >> need to learn enough about the state of the art to ensure that the
> >> discussions can be productive.
> >>
> >
> > I think I demonstrated I am ready to put some effort into this
> >
> > And I think this remark is unfair
>
> I wrote this:
>
> But please do not demand of others to explain everything in detail.
> (I’m directing this at everyone who heeds my advice to go to
> guile-devel, not at any one person in particular.)
>
> Rephrasing: I’d like to point this out to people who take this
> opportunity to bemoan the lack of other features or who disagree with
> what they think are different priorities. You do not feel addressed if
> you know you’ve made efforts in this area.
>
This is another of your points I can't process now
I'll try again later
>
> > And saying I should come on guile-dev and actually provide what I thin is
> > useful, nowing that I can't (not immediately is not a fair answer either
> >
> > Because it's equivalent to a "fuck you"
>
> Wow. No.
>
> I think that’s an *extremely* uncharitable reading of what I wrote. I
> will refrain from further comments in this thread lest what I write will
> be misconstrued in a similar fashion.
>
O, I'll try to clarify this one too.
Just not now
>
> >> With regards to the shouting match on #guile that you linked in your
> >> blog post, I can only say that I would have likely stepped in had this
> >> happened when I was around. Textual communication certainly should not
> >> reach these levels of apparent aggression.
> >>
> >
> > What do you mean with "apparent" ?
>
> I’m pretty bad at gauging emotion in textual communication and it’s
> generally not easy to infer the intended tone in short text messages.
> That said, the exchange you linked to appeared to me to be of an
> aggressive nature. That’s what I mean by “apparent”.
>
It was of an aggressive nature
I was assaulted in an arbitrary, unwarranted and uncalled for way
It was wild
Because I had used G-golf as an example
I had also used Skribilo as another example
You now what Ludo did ?
Instead of calling me an hopeless moron unwilling to learn, he went and
updated Skribilo, without saying a single word
I noticed
And I appreciated it
So, yes, it was aggressie indeed
Again. I'll try to be more complete later
[-- Attachment #2: Type: text/html, Size: 4090 bytes --]
next prev parent reply other threads:[~2018-06-09 13:07 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-07 15:25 my latest blog post Catonano
2018-06-07 16:28 ` Joshua Branson
2018-06-08 4:24 ` Christopher Lemmer Webber
2018-06-08 6:18 ` Fis Trivial
2018-06-08 14:02 ` Ricardo Wurmus
2018-06-08 8:25 ` Catonano
2018-06-08 13:51 ` Fis Trivial
2018-06-08 14:25 ` Ricardo Wurmus
2018-06-09 7:47 ` Catonano
2018-06-09 12:24 ` Ricardo Wurmus
2018-06-09 13:07 ` Catonano [this message]
2018-06-09 15:29 ` Christopher Lemmer Webber
2018-06-09 13:51 ` Christopher Lemmer Webber
2018-06-07 17:03 ` Mark H Weaver
2018-06-07 19:40 ` Catonano
2018-06-08 9:39 ` Nils Gillmann
2018-06-08 9:45 ` Catonano
2018-06-08 18:05 ` Mark H Weaver
2018-06-09 7:00 ` Catonano
2018-06-09 10:39 ` Ricardo Wurmus
2018-06-09 10:52 ` Catonano
2018-06-09 12:14 ` Ricardo Wurmus
2018-06-09 13:03 ` Catonano
2018-06-10 10:53 ` Mark H Weaver
2018-06-07 18:11 ` Thorsten Wilms
2018-06-07 21:45 ` Alex Vong
2018-06-08 9:15 ` Julien Lepiller
2018-06-08 9:34 ` Clément Lassieur
2018-06-08 9:45 ` Julien Lepiller
2018-06-08 13:50 ` Widen info Oleg Pykhalov
2018-06-08 13:59 ` Julien Lepiller
2018-06-08 13:49 ` my latest blog post Ludovic Courtès
2018-06-09 5:59 ` Catonano
2018-06-09 22:49 ` myglc2
2018-06-10 0:51 ` Mark H Weaver
2018-06-10 6:55 ` Pjotr Prins
2018-06-10 9:07 ` Catonano
2018-06-10 9:29 ` Ricardo Wurmus
2018-06-10 9:30 ` Catonano
2018-06-10 10:37 ` Ricardo Wurmus
2018-06-10 10:45 ` Mark H Weaver
2018-06-10 12:06 ` Pjotr Prins
2018-06-10 7:58 ` Catonano
2018-06-10 9:26 ` Ricardo Wurmus
2018-06-10 9:27 ` Catonano
2018-06-10 19:13 ` Ludovic Courtès
2018-06-10 8:07 ` Catonano
2018-06-10 19:23 ` Ludovic Courtès
2018-06-10 8:17 ` my latest blog post [everyone, please take a cooldown break] Nils Gillmann
2018-06-10 13:33 ` Christopher Lemmer Webber
2018-06-10 14:18 ` Gábor Boskovits
2018-06-10 14:37 ` Kei Kebreau
2018-06-11 6:01 ` swedebugia
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=CAJ98PDyquE9PLTVTixyZ7vJ957NPkU_KDEwYkcfEmTObm+0sCA@mail.gmail.com \
--to=catonano@gmail.com \
--cc=guix-devel@gnu.org \
--cc=jbranso@fastmail.com \
--cc=rekado@elephly.net \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.