public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Bernd Edlinger <bernd.edlinger@hotmail.de>
To: Overseers mailing list <overseers@sourceware.org>,
	Arseny Solokha <asolokha@gmx.com>,
	Jonathan Wakely <jwakely.gcc@gmail.com>,
	richard.sandiford@arm.com
Subject: Re: Can we please have the old mailing list back
Date: Thu, 2 Apr 2020 18:12:14 +0200	[thread overview]
Message-ID: <AM6PR03MB51702E3C353027B096CFE5A9E4C60@AM6PR03MB5170.eurprd03.prod.outlook.com> (raw)
In-Reply-To: <20200402160044.GA7609@cgf.cx>

On 4/2/20 6:00 PM, Christopher Faylor wrote:
> [gcc mailing list removed]
> On Thu, Apr 02, 2020 at 12:01:59PM +0200, Bernd Edlinger wrote:
>> On 4/2/20 11:48 AM, Richard Sandiford wrote:
>>> Sorry for the confusion :-)
>>
>> No problem, I know who you are.
> 
> So do I.  Hi Richard!
> 
>> But if I write a mail I spend a lot of time for it, and if it bounces,
>> that work is lost.  This makes a bad start, and the first impression
>> usually decides a lot in our lives.
> 
> Thunderbird, and most other email clients, have a "Sent" folder so this
> is just ridiculous.
> 
> 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?


> I will reiterate the that if there are issues with marc.info, or any
> other non-sourceware.org mailing list archiver they need to be addressed
> with the non-sourceware.org entity.
> 
> If there are issues with email received from sourceware.org/gcc.gnu.org
> like attachments looking funny, then, of course, we will want to hear
> about them.  We care if email doesn't show up in our subscribers inbox
> or if the sourceware.org/gcc.gnu.org archives are incorrect.
> 
> We don't care if attachments look wrong on sites over which we have no
> control.  We don't care if email isn't showing up on other archiving
> sites.  We would certainly listen to concerns from the owners of other
> sites but there are no guarantees that we would change anything to make
> their lives easier.  That's not how this works.
> 
> Your valid point about http vs. https has been corrected.  Future
> attachments will show https.  We'll schedule a mailing list archive
> rebuild at some point to fix the rest. Thanks for  bringing that issue
> to our attention.
> 

  reply	other threads:[~2020-04-02 16:12 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 [this message]
2020-04-02 20:34                                 ` Gerald Pfeifer
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=AM6PR03MB51702E3C353027B096CFE5A9E4C60@AM6PR03MB5170.eurprd03.prod.outlook.com \
    --to=bernd.edlinger@hotmail.de \
    --cc=asolokha@gmx.com \
    --cc=jwakely.gcc@gmail.com \
    --cc=overseers@sourceware.org \
    --cc=richard.sandiford@arm.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 read-only IMAP folder(s) and NNTP newsgroup(s).