From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Ilya Dryomov <idryomov@gmail•com>
Cc: Al Viro <viro@zeniv•linux.org.uk>, Sage Weil <sage@newdream•net>,
linux-next <linux-next@vger•kernel.org>,
"linux-kernel@vger•kernel.org" <linux-kernel@vger•kernel.org>,
"Yan, Zheng" <zyan@redhat•com>
Subject: Re: linux-next: manual merge of the vfs tree with the ceph tree
Date: Fri, 26 Jun 2015 18:33:26 +1000 [thread overview]
Message-ID: <20150626183326.7287706a@canb.auug.org.au> (raw)
In-Reply-To: <CAOi1vP8-Fz2FABJZdt6_aZq_TNGFBhGuanV-n9kBvdFmyRMsyw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1487 bytes --]
Hi Ilya,
On Fri, 26 Jun 2015 11:21:52 +0300 Ilya Dryomov <idryomov@gmail•com> wrote:
>
> > Sage: that ceph tree commit has no Signed-off-by from its
> > committer :-( The same is true for almost all the commits in the ceph
> > tree ... and the committer (Ilya) is not listed as a maintainer of that
> > tree ... and its on github :-(
>
> Well, it has Signed-off-by from a person who is listed as a maintainer
> of fs/ceph (Zheng). We share the same tree for three components: rbd
> (drivers/block/rbd.c), cephfs (fs/ceph) and libceph (net/ceph) which is
> used by both rbd and cephfs (we should probably split libceph into its
> own MAINTAINERS entry). The volume of commits is not that high and
> we prefer to not clutter our 30-40 commits per cycle with a bunch of
> merges, so when one of us rebases the committer stamp gets wiped.
Then the person who rebases it must add a Signed-off-by line since they
are then on the handling path from the author to Linus.
> As for github, is that a bad thing? ceph-client.git is certainly not
> the only github tree in linux-next.
Yeah, it just means that I am a bit more suspicious of things there.
You are *not* listed in my contacts for the ceph tree not are you
listed in the MAINTAINERS file for that tree.
Also the tree listed in MAINTAINERS is:
T: git git://git.kernel.org/pub/scm/linux/kernel/git/sage/ceph-client.git
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-06-26 8:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-26 1:17 linux-next: manual merge of the vfs tree with the ceph tree Stephen Rothwell
2015-06-26 8:21 ` Ilya Dryomov
2015-06-26 8:33 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-10-29 1:16 Stephen Rothwell
2019-08-27 1:06 Stephen Rothwell
2019-08-29 1:25 Stephen Rothwell
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=20150626183326.7287706a@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=idryomov@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sage@newdream$(echo .)net \
--cc=viro@zeniv$(echo .)linux.org.uk \
--cc=zyan@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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