From: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public•gmane.org>
To: Stephen Rothwell <sfr-3FnU+UHB4dNDw9hX6IcOSA@public•gmane.org>,
Paul Gortmaker
<paul.gortmaker-CWA4WttNNZF54TAoqtyWWQ@public•gmane.org>
Cc: Larry Finger
<Larry.Finger-tQ5ms3gMjBLk1uMJSBkQmQ@public•gmane.org>,
linux-next-u79uwXL29TY76Z2rM5mHXA@public•gmane.org,
netdev-u79uwXL29TY76Z2rM5mHXA@public•gmane.org,
linux-wireless-u79uwXL29TY76Z2rM5mHXA@public•gmane.org,
Kalle Valo <kvalo-sgV2jX0FEOL9JmXXK+q4OQ@public•gmane.org>
Subject: Re: [linux-next] rtlwifi commit contains a patch reject file
Date: Tue, 23 Apr 2019 12:15:16 +0200 [thread overview]
Message-ID: <9ebd031d208aae52b787905eb4fb5e04a1d52969.camel@sipsolutions.net> (raw)
In-Reply-To: <20190422125926.15862fdd-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org> (sfid-20190422_045942_518263_99E79F6A)
On Mon, 2019-04-22 at 12:59 +1000, Stephen Rothwell wrote:
> I have added that test to my commit checks now. Thanks for the
> suggestion. So far it only checks for .rej and .orig files - any
> others?
Maybe consider the things listed in the .gitignore file? Those are quite
difficult to add (git add -f) but I think I've seen it happen before,
perhaps through different trees etc.
In fact, *.orig is listed in .gitignore, I wonder why *.rej isn't? Maybe
so it stands out more in "git status"?
johannes
next prev parent reply other threads:[~2019-04-23 10:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-20 15:50 [linux-next] rtlwifi commit contains a patch reject file Paul Gortmaker
2019-04-22 2:59 ` Stephen Rothwell
[not found] ` <20190422125926.15862fdd-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2019-04-23 10:15 ` Johannes Berg [this message]
2019-04-23 5:41 ` Kalle Valo
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=9ebd031d208aae52b787905eb4fb5e04a1d52969.camel@sipsolutions.net \
--to=johannes-cdvu00un1vgdhxzaddlk8q@public$(echo .)gmane.org \
--cc=Larry.Finger-tQ5ms3gMjBLk1uMJSBkQmQ@public$(echo .)gmane.org \
--cc=kvalo-sgV2jX0FEOL9JmXXK+q4OQ@public$(echo .)gmane.org \
--cc=linux-next-u79uwXL29TY76Z2rM5mHXA@public$(echo .)gmane.org \
--cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public$(echo .)gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public$(echo .)gmane.org \
--cc=paul.gortmaker-CWA4WttNNZF54TAoqtyWWQ@public$(echo .)gmane.org \
--cc=sfr-3FnU+UHB4dNDw9hX6IcOSA@public$(echo .)gmane.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