From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: "Andreas Grünbacher" <andreas.gruenbacher@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
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, 12 Dec 2018 10:46:05 -0500 [thread overview]
Message-ID: <20181212154605.GC17249@pure.paranoia.local> (raw)
In-Reply-To: <CAHpGcM+wCSrj0pk89ZoMENp+L_zSXbSFhEJcsdDEOh1F-GmGvg@mail.gmail.com>
On Tue, Dec 11, 2018 at 09:47:43PM +0100, Andreas Grünbacher wrote:
> > Now, after the rebase:
> >
> > Commits
> >
> > 187e4dad3f55 ("gfs2: Remove vestigial bd_ops")
> >
> > is missing a Signed-off-by from its committer.
>
> Yep, I've not asked for a way to get the server to reject or warn
> about such pushes without a reason.
We don't run checks on push that involve iterating through commits,
because most of the pushes we receive are merges and rejecting on a
commit somewhere deep in an octopus merge would just result in angry
maintainers.
Best,
-K
next prev parent reply other threads:[~2018-12-12 15:46 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-11 20:24 linux-next: Signed-off-by missing for commit in the gfs2 tree 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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-08-12 4:44 Stephen Rothwell
2024-12-08 20:24 Stephen Rothwell
2024-10-21 20:50 Stephen Rothwell
2024-10-22 11:23 ` Qianqiang Liu
2024-10-22 11:34 ` Andreas Gruenbacher
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-11-15 22:19 Stephen Rothwell
2018-10-08 20:54 Stephen Rothwell
2018-10-09 12:11 ` Bob Peterson
2018-07-24 22:01 Stephen Rothwell
2018-07-24 22:23 ` Andreas Grünbacher
2018-07-25 1:16 ` Stephen Rothwell
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=20181212154605.GC17249@pure.paranoia.local \
--to=konstantin@linuxfoundation.org \
--cc=agruenba@redhat.com \
--cc=andreas.gruenbacher@gmail.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.