From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTP id 93FF0979 for ; Fri, 23 May 2014 08:02:02 +0000 (UTC) Received: from mail-ob0-f170.google.com (mail-ob0-f170.google.com [209.85.214.170]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 1FAB020242 for ; Fri, 23 May 2014 08:02:02 +0000 (UTC) Received: by mail-ob0-f170.google.com with SMTP id uy5so5071716obc.29 for ; Fri, 23 May 2014 01:02:01 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <20140513162844.GA1647@cloud> References: <20140513162844.GA1647@cloud> Date: Fri, 23 May 2014 10:02:01 +0200 Message-ID: From: Linus Walleij To: josh@joshtriplett.org Content-Type: text/plain; charset=UTF-8 Cc: "ksummit-discuss@lists.linuxfoundation.org" Subject: Re: [Ksummit-discuss] [TOPIC] Guidance for subsystem maintainers List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Tue, May 13, 2014 at 6:28 PM, 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