From: Andreas Arnez <arnez@linux.vnet.ibm.com>
To: "Ulrich Weigand" <uweigand@de.ibm.com>
Cc: palves@redhat.com (Pedro Alves),
jan.kratochvil@redhat.com (Jan Kratochvil),
xdje42@gmail.com (Doug Evans),
gdb-patches@sourceware.org (gdb-patches\@sourceware.org)
Subject: Re: automated testing comment [Re: time to workaround libc/13097 in fsf gdb?]
Date: Thu, 25 Sep 2014 07:11:00 -0000 [thread overview]
Message-ID: <87sijgjhtk.fsf@br87z6lw.de.ibm.com> (raw)
In-Reply-To: <201409241523.s8OFNNjP009931@d06av02.portsmouth.uk.ibm.com> (Ulrich Weigand's message of "Wed, 24 Sep 2014 17:23:23 +0200 (CEST)")
On Wed, Sep 24 2014, Ulrich Weigand wrote:
> Andreas Arnez wrote:
>> On Tue, Sep 23 2014, Pedro Alves wrote:
>>
>> > I think it'd be fine to send the periodic email results/alerts/whatever to:
>> >
>> > https://sourceware.org/ml/gdb-testresults/
>> >
>> > That list hasn't been active in a while, but it's still alive, afaics,
>> > and the point of that list was to collect auto testers' test results.
>>
>> Interesting. Even before I started working on GDB, Andreas Krebbel had
>> set up a bot that sends test results to a different list, and we're
>> still continuing to do so:
>>
>> https://sourceware.org/ml/gdb-testers/
>>
>> Knowing now that there's also gdb-testresults, I wonder whether that
>> ever was a good choice. We could certainly change that, so gdb-testers
>> is freed up for discussions like this one ;-)
>
> Well, I guess that would be because the main web page:
> https://www.sourceware.org/gdb/mailing-lists/
> says:
>
> gdb-testers
> is a list for the announcement of development snapshots and the reporting of test results.
>
> and does not mention gdb-testresults at all.
Right, I also noticed that gdb-testers is mirrored by Gmane (as
comp.gdb.testing) and gdb-testresults is not. I'm puzzled why
gdb-testresults was ever created...
> I think we should agree on one of them, and document it on the web page.
For instance by leaving everything as-is? Or maybe, for clarity, we
should at least drop the obsolete "announcement of development
snapshots" from the list description?
next prev parent reply other threads:[~2014-09-25 7:11 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-11 16:25 time to workaround libc/13097 in fsf gdb? Doug Evans
2014-09-11 16:37 ` Pedro Alves
2014-09-12 11:55 ` Jan Kratochvil
2014-09-12 12:14 ` Pedro Alves
2014-09-12 12:33 ` Jan Kratochvil
2014-09-12 12:46 ` Pedro Alves
2014-09-17 20:10 ` Jan Kratochvil
2014-09-19 14:38 ` Pedro Alves
2014-09-19 14:41 ` Pedro Alves
2014-09-20 21:30 ` Jan Kratochvil
2014-09-21 19:12 ` Pedro Alves
2014-09-21 19:46 ` Pedro Alves
2014-09-23 23:05 ` Doug Evans
2014-09-26 12:09 ` Pedro Alves
2014-09-22 18:35 ` Jan Kratochvil
2014-09-23 11:49 ` Pedro Alves
2014-09-28 13:41 ` Jan Kratochvil
2014-09-29 10:36 ` Pedro Alves
2014-10-03 13:09 ` Gary Benson
2014-10-07 23:16 ` Doug Evans
2014-09-23 12:05 ` Pedro Alves
2014-09-26 12:05 ` Pedro Alves
2014-09-23 10:59 ` automated testing comment [Re: time to workaround libc/13097 in fsf gdb?] Jan Kratochvil
2014-09-23 12:32 ` Pedro Alves
2014-09-23 12:45 ` Jan Kratochvil
2014-09-23 13:30 ` Pedro Alves
2014-09-23 13:57 ` Jan Kratochvil
2014-09-23 14:48 ` Pedro Alves
2014-09-23 15:53 ` Jan Kratochvil
2014-09-23 15:56 ` Pedro Alves
2014-09-24 13:22 ` Andreas Arnez
2014-09-24 15:23 ` Ulrich Weigand
2014-09-25 7:11 ` Andreas Arnez [this message]
2014-09-25 8:20 ` Pedro Alves
2014-09-25 10:52 ` Jan Kratochvil
2014-09-23 14:54 ` Doug Evans
2014-09-23 15:16 ` Simon Marchi
2014-09-23 14:48 ` Doug Evans
2014-09-23 14:59 ` Pedro Alves
2014-09-20 19:50 ` time to workaround libc/13097 in fsf gdb? Jan Kratochvil
2014-09-23 11:18 ` Pedro Alves
2014-09-23 13:16 ` Gary Benson
2014-10-09 20:09 ` Jan Kratochvil
2014-10-09 22:07 ` Pedro Alves
2014-09-13 1:06 ` Doug Evans
2014-09-17 20:13 ` Jan Kratochvil
2014-09-23 21:35 ` Doug Evans
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=87sijgjhtk.fsf@br87z6lw.de.ibm.com \
--to=arnez@linux.vnet.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=palves@redhat.com \
--cc=uweigand@de.ibm.com \
--cc=xdje42@gmail.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).