From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Guenter Roeck <linux@roeck-us.net>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] new topic: regression test infrastructure? (was Draft Maintainer's Summit Agenda and Attendees - )
Date: Tue, 16 Oct 2018 17:46:33 -0400 [thread overview]
Message-ID: <20181016214633.GE14947@thunk.org> (raw)
In-Reply-To: <20181016211446.GA28549@roeck-us.net>
On Tue, Oct 16, 2018 at 02:14:46PM -0700, Guenter Roeck wrote:
>
> In Edinburgh: https://elinux.org/Automated_Testing_Summit
> In Vancouver: https://blog.linuxplumbersconf.org/2018/testing-and-fuzzing-mc/
>
> While is it good to see the increased interest in testing, I am not
> sure if it makes sense to add yet another venue to discuss it.
I had forgotten about the Testing and Fuzzing MC at Plumber's. I
agree that's probably the right place to be having those discussions.
If the miniconference's schedule is already packed full, we could
probably schedule a kernel summit track, but it's probably better to
keep it all at the MC, since all of the right people will hopefully
there.
Cheers,
- Ted
next prev parent reply other threads:[~2018-10-16 21:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-16 2:12 [Ksummit-discuss] Draft Maintainer's Summit Agenda and Attendees Theodore Y. Ts'o
2018-10-16 8:11 ` Daniel Vetter
2018-10-16 15:13 ` James Bottomley
2018-10-16 18:00 ` Josh Triplett
2018-10-16 18:19 ` James Bottomley
2018-10-16 18:38 ` Tim.Bird
2018-10-16 18:46 ` Josh Triplett
2018-10-16 18:57 ` Daniel Vetter
2018-10-16 18:52 ` James Bottomley
2018-10-16 18:16 ` Mark Brown
2018-10-16 18:36 ` Chris Mason
2018-10-16 19:53 ` [Ksummit-discuss] new topic: regression test infrastructure? (was Draft Maintainer's Summit Agenda and Attendees - ) Christian Borntraeger
2018-10-16 20:51 ` Theodore Y. Ts'o
2018-10-16 21:11 ` Jiri Kosina
2018-10-16 21:14 ` Guenter Roeck
2018-10-16 21:46 ` Theodore Y. Ts'o [this message]
2018-10-17 0:08 ` Michael Ellerman
2018-10-17 1:06 ` Tim.Bird
2018-10-17 1:51 ` Shuah Khan
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=20181016214633.GE14947@thunk.org \
--to=tytso@mit.edu \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=linux@roeck-us.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.
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.