linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Tobin C. Harding" <me@tobin.cc>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Signed-off-by missing for commit in the leaks tree
Date: Thu, 14 Feb 2019 19:33:35 +1100	[thread overview]
Message-ID: <20190214083335.GA3053@eros.localdomain> (raw)
In-Reply-To: <20190214183605.3132886d@canb.auug.org.au>

[-- Attachment #1: Type: text/plain, Size: 267 bytes --]

On Thu, Feb 14, 2019 at 06:36:05PM +1100, Stephen Rothwell wrote:
> Hi Tobin,
> 
> Commit
> 
>   5d06b3fc8e61 ("leaking_addresses: Completely remove --version flag")
> 
> is missing a Signed-off-by from its author and committer.

Thanks, fixed.

	Tobin


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2019-02-14  8:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-14  7:36 linux-next: Signed-off-by missing for commit in the leaks tree Stephen Rothwell
2019-02-14  8:33 ` Tobin C. Harding [this message]

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=20190214083335.GA3053@eros.localdomain \
    --to=me@tobin.cc \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).