netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: techsupport@mycode.ai
Cc: kuznet@ms2.inr.ac.ru, yoshfuji@linux-ipv6.org, netdev@vger.kernel.org
Subject: Re: [PATCH] Remove useless assignment in ip_do_fragment
Date: Fri, 23 Feb 2018 10:57:45 -0500 (EST)	[thread overview]
Message-ID: <20180223.105745.425252686693023825.davem@davemloft.net> (raw)
In-Reply-To: <1519319425-30431-1-git-send-email-benjamin.bales@assrc.us>

From: C0deAi <techsupport@mycode.ai>
Date: Thu, 22 Feb 2018 12:10:25 -0500

> Hi my name is Benjamin Bales.
> 
> I am the founder and creator of CodeAI,
> the first non-human contributor to your software project. CodeAI finds
> and fixes security defects for you. It fixed 327. It wants to merge a
> fix for a useless assignment. To view all 327 fixed issues from the
> run claim your free open source account at mycode.ai and the
> Dockerfile used to build and run your project in CodeAI, here-
> https://drive.google.com/drive/folders/1KB9WQQyWQgYccmiSjy2E1JWJ4vWuoLYd .
> It is always free for open source projects.
> 
> If you have any questions about these results or have general
> inquiries about CodeAI, please send an email to techsupport@mycode.ai
> 
> Signed-off-by: Benjamin Bales <techsupport@mycode.ai>

Sorry, I'm not applying code emitted by a machine, and definitely not
with commit messages that look like this.

In particular, promoting your service in a commit message is
incredibly inappropriate.

All patch postings should be submitted by a human being, even if they
came from something which was machine generated.

  reply	other threads:[~2018-02-23 15:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-22 17:10 [PATCH] Remove useless assignment in ip_do_fragment C0deAi
2018-02-23 15:57 ` David Miller [this message]
2018-02-27 16:20   ` Code AI

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=20180223.105745.425252686693023825.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=netdev@vger.kernel.org \
    --cc=techsupport@mycode.ai \
    --cc=yoshfuji@linux-ipv6.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 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).