From: Kieran Bingham <kieran@ksquared.org.uk>
To: Omar Sandoval <osandov@osandov.com>, Jan Kiszka <jan.kiszka@siemens.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scripts/gdb: add constants.py to .gitignore
Date: Tue, 21 Jun 2016 21:56:36 +0100 [thread overview]
Message-ID: <5769AA04.2020505@bingham.xyz> (raw)
In-Reply-To: <a16d95d6c75579653b8a5bee56d753e97fce1d7a.1466452743.git.osandov@fb.com>
Hi Omar,
Thanks for spotting, and submitting this.
On 20/06/16 21:00, Omar Sandoval wrote:
> From: Omar Sandoval <osandov@fb.com>
>
> Since scripts/gdb/linux/constants.py is autogenerated, this should have
> been added to .gitignore when it was introduced.
Absolutely! - This never hit me, as I always build out-of-tree
> Fixes: f197d75fcad1 ("scripts/gdb: provide linux constants")
> Signed-off-by: Omar Sandoval <osandov@fb.com>
Unfortunately - Nacked on the principle of the comment in the top of the
.gitignore file:
# NOTE! Don't add files that are generated in specific
# subdirectories here. Add them in the ".gitignore" file
# in that subdirectory instead.
Could you fix this up (meaning add to the .gitignore under
scripts/gdb/linux) and resend please?
Then I'll add to my queue to send as fixes for current.
(which I'm hoping to get sent before the weekend, or at the weekend)
> ---
> .gitignore | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/.gitignore b/.gitignore
> index 0c320bf02586..5cdccb07e3a3 100644
> --- a/.gitignore
> +++ b/.gitignore
> @@ -112,3 +112,6 @@ all.config
>
> # Kdevelop4
> *.kdev4
> +
> +# Generated for CONFIG_GDB_SCRIPTS
> +/scripts/gdb/linux/constants.py
>
--
Regards
Kieran Bingham
prev parent reply other threads:[~2016-06-21 22:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-20 20:00 [PATCH] scripts/gdb: add constants.py to .gitignore Omar Sandoval
2016-06-21 20:56 ` Kieran Bingham [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=5769AA04.2020505@bingham.xyz \
--to=kieran@ksquared.org.uk \
--cc=jan.kiszka@siemens.com \
--cc=linux-kernel@vger.kernel.org \
--cc=osandov@osandov.com \
/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