linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Stephen Rothwell <sfr@canb.auug.org.au>, Greg KH <greg@kroah.com>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Signed-off-by missing for commits in the staging tree
Date: Wed, 29 Nov 2017 11:09:04 +1100	[thread overview]
Message-ID: <87609uymhr.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <20171129095916.062d6f7d@canb.auug.org.au>

Stephen Rothwell <sfr@canb.auug.org.au> writes:

> Hi Greg,
>
> On Tue, 28 Nov 2017 20:41:39 +0100 Greg KH <greg@kroah.com> wrote:
>>
>> I need to set up a git hook for this :(
>
> I couldn't find an appropriate hook for fetching or merging other
> trees :-( Instead I run the attached script below after each fetch.

Isn't the update hook what you want?

Called by git-receive-pack:

   Before each ref is updated, if $GIT_DIR/hooks/update file exists and
   is executable, it is invoked once per ref, with three parameters:

       $GIT_DIR/hooks/update refname sha1-old sha1-new

cheers

  reply	other threads:[~2017-11-29  0:09 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-27 21:16 linux-next: Signed-off-by missing for commits in the staging tree Stephen Rothwell
2017-11-28 19:41 ` Greg KH
2017-11-28 22:59   ` Stephen Rothwell
2017-11-29  0:09     ` Michael Ellerman [this message]
2017-11-29  0:18       ` Stephen Rothwell
2018-02-23  9:17     ` Greg KH
2017-11-29  8:44   ` Christian Gromm
2017-11-29  9:14     ` Greg KH
2017-11-29  9:25       ` Christian Gromm
2017-11-29  9:32         ` Greg KH
2017-11-29 12:24     ` Stephen Rothwell
2017-11-29 12:35       ` Stephen Rothwell
2017-11-29 12:42       ` Christian Gromm
  -- strict thread matches above, loose matches on Subject: below --
2018-01-09 20:18 Stephen Rothwell
2018-01-11 17:50 ` Greg KH
2017-09-18 21:54 Stephen Rothwell
2017-09-19  6:09 ` Greg KH
2017-09-19 15:34   ` Tobin Harding
2017-09-19 15:50     ` Tobin Harding

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=87609uymhr.fsf@concordia.ellerman.id.au \
    --to=mpe@ellerman.id.au \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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 NNTP newsgroup(s).