From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Jarkko Sakkinen <jarkko.sakkinen@linux•intel.com>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: Re: linux-next: unsigned commits in tpmdd tree
Date: Thu, 3 Mar 2016 07:34:41 +1100 [thread overview]
Message-ID: <20160303073441.5ba3aa0d@canb.auug.org.au> (raw)
In-Reply-To: <20160302142956.GA8341@intel.com>
Hi Jarkko,
On Wed, 2 Mar 2016 16:29:56 +0200 Jarkko Sakkinen <jarkko.sakkinen@linux•intel.com> wrote:
>
> On Wed, Mar 02, 2016 at 07:42:18AM +1100, Stephen Rothwell wrote:
> > Hi Jarkko,
> >
> > All the new commits in you tree today have no Signed-off-by from you as
> > the committer.
>
> Oops :( This is my mistake. Do you want me to do git reverts and redo
> commits?
Reverting doesn't really fix the problem (since eth original commits
would still be there), you would have to rebase (maybe onto the same
base commit) all the commits and add the Signed-off-by lines.
--
Cheers,
Stephen Rothwell
next prev parent reply other threads:[~2016-03-02 20:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-01 20:42 linux-next: unsigned commits in tpmdd tree Stephen Rothwell
2016-03-02 14:29 ` Jarkko Sakkinen
2016-03-02 20:34 ` Stephen Rothwell [this message]
2016-03-03 10:14 ` Jarkko Sakkinen
2016-03-03 22:48 ` 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=20160303073441.5ba3aa0d@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=jarkko.sakkinen@linux$(echo .)intel.com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/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