All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andreas Grünbacher" <andreas.gruenbacher@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Steven Whitehouse <swhiteho@redhat.com>,
	Bob Peterson <rpeterso@redhat.com>,
	Linux-Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andreas Gruenbacher <agruenba@redhat.com>
Subject: Re: linux-next: Signed-off-by missing for commit in the gfs2 tree
Date: Wed, 25 Jul 2018 00:23:22 +0200	[thread overview]
Message-ID: <CAHpGcM+WkOKkd+GLMiTWsvnLA_daY_5pBfSQp_KYoPVcRQQHGg@mail.gmail.com> (raw)
In-Reply-To: <20180725080130.314f62bb@canb.auug.org.au>

Hi Stephen,

2018-07-25 0:01 GMT+02:00 Stephen Rothwell <sfr@canb.auug.org.au>:
> Hi all,
>
> Commit
>
>   b6fbc2f6a686 ("GFS2: Fix recovery issues for spectators")
>
> is missing a Signed-off-by from its committer.  It was rebased.

thanks, I've fixed it now but this is getting rather annoying -- and
it must happen to others as well. Do you happen to have git hooks that
prevent this from happening?

Thanks,
Andreas

  reply	other threads:[~2018-07-24 22:23 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-24 22:01 linux-next: Signed-off-by missing for commit in the gfs2 tree Stephen Rothwell
2018-07-24 22:23 ` Andreas Grünbacher [this message]
2018-07-25  1:16   ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2023-12-21 21:33 Stephen Rothwell
2023-08-17 22:50 Stephen Rothwell
2023-08-14 22:55 Stephen Rothwell
2023-06-29 22:02 Stephen Rothwell
2023-01-31 21:37 Stephen Rothwell
2022-06-23 23:37 Stephen Rothwell
2022-06-02 22:12 Stephen Rothwell
2022-03-27 21:17 Stephen Rothwell
2022-02-13 10:52 Stephen Rothwell
2021-11-06  2:08 Stephen Rothwell
2021-01-24  9:50 Stephen Rothwell
2020-12-29 20:22 Stephen Rothwell
2020-10-20 20:35 Stephen Rothwell
2020-09-20 20:09 Stephen Rothwell
2020-09-16 21:31 Stephen Rothwell
2020-05-10 20:53 Stephen Rothwell
2020-04-15 21:53 Stephen Rothwell
2019-05-07 21:36 Stephen Rothwell
2018-12-11 20:24 Stephen Rothwell
2018-12-11 20:38 ` Stephen Rothwell
2018-12-11 20:47   ` Andreas Grünbacher
2018-12-11 22:51     ` Stephen Rothwell
2018-12-12 15:46     ` Konstantin Ryabitsev
2018-11-15 22:19 Stephen Rothwell
2018-10-08 20:54 Stephen Rothwell
2018-10-09 12:11 ` Bob Peterson
2018-01-16 20:51 Stephen Rothwell
2018-01-17  9:36 ` Steven Whitehouse
2018-01-17 14:46   ` Bob Peterson

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=CAHpGcM+WkOKkd+GLMiTWsvnLA_daY_5pBfSQp_KYoPVcRQQHGg@mail.gmail.com \
    --to=andreas.gruenbacher@gmail.com \
    --cc=agruenba@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rpeterso@redhat.com \
    --cc=sfr@canb.auug.org.au \
    --cc=swhiteho@redhat.com \
    /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.