stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "Enrico Weigelt, metux IT consult" <info@metux.net>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH] .gitignore: add some missing excludes
Date: Tue, 22 Jan 2019 16:25:45 +0100	[thread overview]
Message-ID: <20190122152545.GC17676@kroah.com> (raw)
In-Reply-To: <1548169712-24909-1-git-send-email-info@metux.net>

On Tue, Jan 22, 2019 at 04:08:32PM +0100, Enrico Weigelt, metux IT consult wrote:
> For now they're all catched by ".*", but some folks might remove
> that in order to add their own .config file.
> 
> Signed-off-by: Enrico Weigelt, metux IT consult <info@metux.net>
> ---
>  .gitignore                 | 6 ++++++
>  scripts/kconfig/.gitignore | 1 +
>  2 files changed, 7 insertions(+)

Why did you send this here?

This isn't how to send kernel patches, please read the kernel
documentation for how to do that properly.

thanks,

greg k-h

      reply	other threads:[~2019-01-22 15:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-22 15:08 [PATCH] .gitignore: add some missing excludes Enrico Weigelt, metux IT consult
2019-01-22 15:25 ` Greg KH [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=20190122152545.GC17676@kroah.com \
    --to=greg@kroah.com \
    --cc=info@metux.net \
    --cc=stable@vger.kernel.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).