From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22025 invoked by alias); 18 Nov 2005 18:36:46 -0000 Received: (qmail 21927 invoked by uid 22791); 18 Nov 2005 18:36:39 -0000 Received: from romy.inter.net.il (HELO romy.inter.net.il) (192.114.186.66) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Fri, 18 Nov 2005 18:36:39 +0000 Received: from HOME-C4E4A596F7 (IGLD-84-228-161-34.inter.net.il [84.228.161.34]) by romy.inter.net.il (MOS 3.5.8-GR) with ESMTP id CZT79192 (AUTH halo1); Fri, 18 Nov 2005 20:31:30 +0200 (IST) Date: Fri, 18 Nov 2005 18:36:00 -0000 Message-Id: From: Eli Zaretskii To: pgilliam@us.ibm.com CC: gdb@sourceware.org, brobecker@adacore.com, cagney@gnu.org, jtc@acorntoolworks.com, fnf@ninemoons.com, Peter.Schauer@regent.e-technik.tu-muenchen.de, ezannoni@redhat.com In-reply-to: <200511180956.14917.pgilliam@us.ibm.com> (message from Paul Gilliam on Fri, 18 Nov 2005 09:56:14 -0800) Subject: Re: Maintainer policy for GDB Reply-to: Eli Zaretskii References: <20051117044801.GA4705@nevyn.them.org> <20051117231020.GJ1635@adacore.com> <200511180956.14917.pgilliam@us.ibm.com> X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2005-11/txt/msg00397.txt.bz2 > From: Paul Gilliam > Date: Fri, 18 Nov 2005 09:56:14 -0800 > Cc: Joel Brobecker , cagney@gnu.org, > jtc@acorntoolworks.com, fnf@ninemoons.com, > Peter.Schauer@regent.e-technik.tu-muenchen.de, ezannoni@redhat.com > > On Friday 18 November 2005 04:39, Eli Zaretskii wrote: > > > Date: Thu, 17 Nov 2005 15:10:20 -0800 > > > From: Joel Brobecker > > > > > > About the voting system: I would also prefer to avoid this. The history > > > of the GDB maintenance community since I joined shows that we're able > > > to work together without unsolvable disagreements. > > > > How far into the past does your history go? I've seen unsolvable > > disagreements less than a year ago. > > Do you have a URL into the mailing list archive? I started to look for it, but then I read your other comments and realized that you were mocking me. So I won't bother looking for the relevant messages. Some of them were in private mail, so there's no URLs anyway. But reality doesn't change if there's no URL to show as evidence. If you don't believe me that these things happened, ask others here, they will tell you. > Is there a technological solution to this problem? Something that could > tell if a person were NOT subscribed to the list and send the mail directly? I don't know of any technological solution, except to configure the list server to filter addresses in order to prevent multiple messages. Most mailing lists don't do that, and FWIW I'm used to have double messages, they don't annoy me. That's why I cannot understand why people bother to use Mail-Followup-To. IMHO it causes more trouble than it's worth.