From: Tao Ma <tao.ma@oracle.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Mark Fasheh <mfasheh@suse.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [GIT PULL] ocfs2 fixes for 2.6.36.
Date: Wed, 08 Sep 2010 14:48:50 +0800 [thread overview]
Message-ID: <4C8731D2.1030002@oracle.com> (raw)
In-Reply-To: <AANLkTi=VaR=UUYh3hzKdD+tvKuuTCD4b4qufQ03AWWxQ@mail.gmail.com>
Hi Linus,
On 09/08/2010 10:19 AM, Linus Torvalds wrote:
> On Tue, Sep 7, 2010 at 4:41 PM, Joel Becker<boel.becker@oracle.com> wrote:
>>
>> Here are the ocfs2 fixes we have ready for pulling right now. I
>> have a bit of a procedural question, though. I've been busy, so Tao was
>> kind enough to take the fixes I already had and apply all the new fixes.
>> He coordinated testing them and getting them ready to go upstream.
>> That's why I have his git tree in the pull request below.
>> I wasn't sure how the signoffs work for this. He's got signoffs
>> on the stuff he put together, because it's coming through his tree. My
>> naive assumption is that this is the correct way to go.
>
> The sign-off chain should basically stretch from the author to the
> committer - so a good sign-off chain is one where the first sign-off
> matches the author of the commit, and the last sign-off matches the
> committer, and the ones in the middle are obviously the path it took
> from one to the other.
>
> However, Tao has *NOT* added sign-offs to the patches he's taken. I
> didn't look at all of them, but the first few commits are all authored
> (and signed off on - so far so good) by Mark Fasheh, but there is no
> sign-off for Tao. So the sign-off chain is clearly not complete.
sorry for the trouble. This is the first time for me to collect patches
for a mainline upstream.
So I have added my sign-off to all the patches whose author isn't me to
indicate that I am the committer. Hope it works. please pull
git://oss.oracle.com/git/tma/linux-2.6.git fixes
REgards,
Tao
WARNING: multiple messages have this Message-ID (diff)
From: Tao Ma <tao.ma@oracle.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Mark Fasheh <mfasheh@suse.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, ocfs2-devel@oss.oracle.com
Subject: Re: [GIT PULL] ocfs2 fixes for 2.6.36.
Date: Wed, 08 Sep 2010 14:48:50 +0800 [thread overview]
Message-ID: <4C8731D2.1030002@oracle.com> (raw)
In-Reply-To: <AANLkTi=VaR=UUYh3hzKdD+tvKuuTCD4b4qufQ03AWWxQ@mail.gmail.com>
Hi Linus,
On 09/08/2010 10:19 AM, Linus Torvalds wrote:
> On Tue, Sep 7, 2010 at 4:41 PM, Joel Becker<boel.becker@oracle.com> wrote:
>>
>> Here are the ocfs2 fixes we have ready for pulling right now. I
>> have a bit of a procedural question, though. I've been busy, so Tao was
>> kind enough to take the fixes I already had and apply all the new fixes.
>> He coordinated testing them and getting them ready to go upstream.
>> That's why I have his git tree in the pull request below.
>> I wasn't sure how the signoffs work for this. He's got signoffs
>> on the stuff he put together, because it's coming through his tree. My
>> naive assumption is that this is the correct way to go.
>
> The sign-off chain should basically stretch from the author to the
> committer - so a good sign-off chain is one where the first sign-off
> matches the author of the commit, and the last sign-off matches the
> committer, and the ones in the middle are obviously the path it took
> from one to the other.
>
> However, Tao has *NOT* added sign-offs to the patches he's taken. I
> didn't look at all of them, but the first few commits are all authored
> (and signed off on - so far so good) by Mark Fasheh, but there is no
> sign-off for Tao. So the sign-off chain is clearly not complete.
sorry for the trouble. This is the first time for me to collect patches
for a mainline upstream.
So I have added my sign-off to all the patches whose author isn't me to
indicate that I am the committer. Hope it works. please pull
git://oss.oracle.com/git/tma/linux-2.6.git fixes
REgards,
Tao
next prev parent reply other threads:[~2010-09-08 6:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-07 23:41 [Ocfs2-devel] [GIT PULL] ocfs2 fixes for 2.6.36 Joel Becker
2010-09-07 23:41 ` Joel Becker
2010-09-08 2:19 ` [Ocfs2-devel] " Linus Torvalds
2010-09-08 2:19 ` Linus Torvalds
2010-09-08 6:48 ` Tao Ma [this message]
2010-09-08 6:48 ` Tao Ma
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=4C8731D2.1030002@oracle.com \
--to=tao.ma@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mfasheh@suse.com \
--cc=ocfs2-devel@oss.oracle.com \
--cc=torvalds@linux-foundation.org \
/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.