From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Josh Triplett <josh@joshtriplett.org>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [ANNOUNCE] git-series: track changes to a patch series over time
Date: Mon, 8 Aug 2016 17:10:10 -0700 [thread overview]
Message-ID: <20160809001010.GA23815@linux.vnet.ibm.com> (raw)
In-Reply-To: <20160729150522.GC12137@x>
On Fri, Jul 29, 2016 at 08:05:22AM -0700, Josh Triplett wrote:
> On Fri, Jul 29, 2016 at 07:55:44AM -0700, James Bottomley wrote:
> > On Fri, 2016-07-29 at 00:50 -0700, Josh Triplett wrote:
> > > I'd welcome any feedback, whether on the interface and workflow, the
> > > internals and collaboration, ideas on presenting diffs of patch
> > > series, or anything else.
> >
> > I've got an offer for you: The Plumbers PC has been kicking around the
> > idea of a git MC at Plumbers. We got as far ask asking Junio Hamano,
> > who said he'd commit to coming, but didn't want to run the MC. Would
> > you be interested in running it? Since it's a barely formed idea at
> > the moment, it would still have to go through the usual Plumbers
> > process of proposing it on
> >
> > http://wiki.linuxplumbersconf.org/2016:topics
> >
> > And then getting formal plumbers PC acceptance (Paul McKenney shepherds
> > this). You can put me down as a committed attendee because, like a lot
> > of people, I have quite a bit of scripting around my git infrastructure
> > which, I suspect, could be shared.
>
> I'd mentioned the idea of a git MC to Paul, and I'd be happy to give a
> git-series presentation/BoF at one, but I don't have the bandwidth to
> run one.
Which is exactly how the MC proposal came to be. ;-)
Kate Stewart took over the shepherding and has found a runner, so here is
hoping that this will actually happen!
Thanx, Paul
next prev parent reply other threads:[~2016-08-09 0:10 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-29 7:50 Josh Triplett
2016-07-29 12:20 ` David Howells
2016-07-29 13:11 ` Josh Triplett
2016-08-04 22:46 ` Catalin Marinas
2016-08-04 23:07 ` Michael S. Tsirkin
2016-08-08 17:27 ` Catalin Marinas
2016-08-15 23:44 ` Michael S. Tsirkin
2016-08-04 23:46 ` Josh Triplett
2016-08-08 17:37 ` Catalin Marinas
2016-07-29 14:06 ` David Howells
2016-07-29 14:21 ` Christoph Lameter
2016-07-29 14:37 ` Josh Triplett
2016-07-29 15:00 ` Daniel Vetter
2016-07-29 15:18 ` Josh Triplett
2016-07-29 15:40 ` Daniel Vetter
2016-07-29 16:21 ` Josh Triplett
2016-07-29 16:31 ` Luis R. Rodriguez
2016-07-29 17:52 ` Bird, Timothy
2016-07-29 17:57 ` James Bottomley
2016-07-29 21:59 ` James Hogan
2016-07-30 2:55 ` Steven Rostedt
2016-07-29 20:13 ` David Howells
2016-07-30 5:02 ` Josh Triplett
2016-07-30 8:43 ` Arnd Bergmann
2016-08-04 12:44 ` Jani Nikula
2016-07-29 14:34 ` Josh Triplett
2016-07-29 14:37 ` David Howells
2016-07-29 14:56 ` Josh Triplett
2016-07-29 14:55 ` James Bottomley
2016-07-29 15:05 ` Josh Triplett
2016-08-09 0:10 ` Paul E. McKenney [this message]
2016-07-29 15:26 ` James Hogan
2016-08-04 23:52 ` Michael S. Tsirkin
2016-08-05 20:26 ` Josh Triplett
2016-08-15 13:20 ` James Hogan
2016-08-15 16:14 ` Josh Triplett
2016-08-15 23:42 ` Michael S. Tsirkin
2016-08-15 12:53 ` James Hogan
2016-08-15 16:34 ` Josh Triplett
2016-08-15 18:46 ` James Hogan
2016-08-15 21:35 ` Josh Triplett
2016-08-15 22:06 ` James Hogan
2016-08-15 23:59 ` Josh Triplett
2016-08-16 2:38 ` Michael S. Tsirkin
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=20160809001010.GA23815@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=josh@joshtriplett.org \
--cc=ksummit-discuss@lists.linuxfoundation.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