public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@pfeifer.com>
To: overseers@sourceware.org, Bernd Edlinger <bernd.edlinger@hotmail.de>
Subject: Re: Can we please have the old mailing list back
Date: Thu, 2 Apr 2020 22:34:28 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LSU.2.21.2004022122270.5927@anthias.pfeifer.com> (raw)
In-Reply-To: <AM6PR03MB51702E3C353027B096CFE5A9E4C60@AM6PR03MB5170.eurprd03.prod.outlook.com>

On Thu, 2 Apr 2020, Bernd Edlinger via Overseers wrote:
>> I'm not going to respond to most of the other points.  Having a public
>> discussion about someone's inconvenience with my email address is silly.
> how about also apologizing for the silly-word here?

May I suggest to take a deep breath?

This thread started on the wrong foot, and while I think I understand 
where you came from, Bernd, I also believe some of your statements 
came across stronger and more emotional than you may have intended.

Many of us here are volunteers, doing this on our own time, and all
of us want to improve GCC and the infrastructure (gcc.gnu.org and
otherwise) - in our different ways.

I, for one, appreciate the work you have been doing and equally how
Christopher and others have been taking care of our infrastructure.

Thank you!
Gerald

  reply	other threads:[~2020-04-02 20:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AM6PR03MB51706DF91E0ECE88B07C0389E4CE0@AM6PR03MB5170.eurprd03.prod.outlook.com>
     [not found] ` <CAH6eHdSvT1TsvQDTnUBU2J-bz8frGPdxeEPUH2MN0YHwEY0OCQ@mail.gmail.com>
     [not found]   ` <AM6PR03MB51707CDB1C1A796575F0BD11E4CE0@AM6PR03MB5170.eurprd03.prod.outlook.com>
     [not found]     ` <AM6PR03MB5170F2D588FE7BA176D4336AE4CE0@AM6PR03MB5170.eurprd03.prod.outlook.com>
     [not found]       ` <23b63bb3-9156-5a28-30b0-8fe557b33df1@gmx.com>
     [not found]         ` <20200325185527.GB8416@cgf.cx>
     [not found]           ` <AM6PR03MB5170D00AC63E74872A13A54FE4CE0@AM6PR03MB5170.eurprd03.prod.outlook.com>
     [not found]             ` <20200326151602.GA8097@cgf.cx>
     [not found]               ` <AM6PR03MB51700731D3005C747ADFED54E4CF0@AM6PR03MB5170.eurprd03.prod.outlook.com>
     [not found]                 ` <AM6PR03MB5170559115186755A61B9414E4C90@AM6PR03MB5170.eurprd03.prod.outlook.com>
     [not found]                   ` <AM6PR03MB5170CA4732A66BF9E240FA9CE4C90@AM6PR03MB5170.eurprd03.prod.outlook.com>
     [not found]                     ` <mptftdm45xk.fsf@arm.com>
2020-04-02  9:33                       ` Bernd Edlinger
2020-04-02  9:48                         ` Richard Sandiford
2020-04-02 10:01                           ` Bernd Edlinger
2020-04-02 16:00                             ` Christopher Faylor
2020-04-02 16:12                               ` Bernd Edlinger
2020-04-02 20:34                                 ` Gerald Pfeifer [this message]
2020-04-02 20:47                                   ` Christopher Faylor
2020-04-03  5:25                                     ` Bernd Edlinger
2020-04-02 21:25                                   ` Bernd Edlinger

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=alpine.LSU.2.21.2004022122270.5927@anthias.pfeifer.com \
    --to=gerald@pfeifer.com \
    --cc=bernd.edlinger@hotmail.de \
    --cc=overseers@sourceware.org \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).