ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: josh@joshtriplett.org
Cc: "ksummit-discuss@lists.linuxfoundation.org"
	<ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [TOPIC] Guidance for subsystem maintainers
Date: Fri, 23 May 2014 10:02:01 +0200	[thread overview]
Message-ID: <CACRpkdYfpLfqTVu9h2ktL2B-4ofBjEhu2sc5F1yphGs81rkA9A@mail.gmail.com> (raw)
In-Reply-To: <20140513162844.GA1647@cloud>

On Tue, May 13, 2014 at 6:28 PM,  <josh@joshtriplett.org> wrote:

>  For instance, what about having
> easy-to-enable git hooks on git.kernel.org similar to those Andrew and
> Greg use, notifying the patch submitter when a maintainer merges their
> patch?  Maintainers could opt into those hooks specifically for
> whichever repository has their "will go upstream eventually" branches,
> and supply a short description of where patches typically flow from
> their tree so submitters know what to expect.

That would be awesome.

Yours,
Linus Walleij

      parent reply	other threads:[~2014-05-23  8:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-13 13:27 Takashi Iwai
2014-05-13 14:31 ` Jiri Kosina
2014-05-13 14:55   ` Takashi Iwai
2014-05-13 14:57   ` Sarah A Sharp
2014-05-13 15:11     ` Laurent Pinchart
2014-05-13 15:32       ` Stephen Warren
2014-05-13 16:28     ` josh
2014-05-13 16:53       ` Olof Johansson
2014-05-13 18:06       ` Jiri Kosina
2014-05-13 19:02       ` Mark Brown
2014-05-16  3:18       ` Jason Cooper
2014-05-18 15:09       ` Mauro Carvalho Chehab
2014-05-20 16:06         ` Josh Triplett
2014-05-23  8:02       ` Linus Walleij [this message]

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=CACRpkdYfpLfqTVu9h2ktL2B-4ofBjEhu2sc5F1yphGs81rkA9A@mail.gmail.com \
    --to=linus.walleij@linaro.org \
    --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