Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: kaszak at gmail.com <kaszak@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Handle defconfig as .config in .gitignore and distclean.
Date: Wed, 20 May 2015 10:45:27 +0200	[thread overview]
Message-ID: <555c49ac.0a64b40a.3499.ffffb3f0@mx.google.com> (raw)

From: Karoly Kasza <kaszak@gmail.com>

After using "make safedefconfig", a defconfig file appears which is an
extract of the .config file. When running git, it incorrectly detects it as a
source code change, while make distclean forgets to remove it.

This patch adds /defconfig to .gitignore and to the distclean Makefile target.

Signed-off-by: Karoly Kasza <kaszak@gmail.com>
---
 .gitignore |    1 +
 Makefile   |    2 +-
 2 files changed, 2 insertions(+), 1 deletion(-)

diff --git a/.gitignore b/.gitignore
index bb02d9f..66f5ac1 100644
--- a/.gitignore
+++ b/.gitignore
@@ -5,6 +5,7 @@
 /.config.old
 /..config.tmp
 /.config
+/defconfig
 *.depend
 *.o
 /*.patch
diff --git a/Makefile b/Makefile
index 5c4293b..bc890dd 100644
--- a/Makefile
+++ b/Makefile
@@ -814,7 +814,7 @@ endif
 ifeq ($(O),output)
 	rm -rf $(O)
 endif
-	rm -rf $(BR2_CONFIG) $(CONFIG_DIR)/.config.old $(CONFIG_DIR)/..config.tmp \
+	rm -rf $(BR2_CONFIG) $(CONFIG_DIR)/defconfig $(CONFIG_DIR)/.config.old $(CONFIG_DIR)/..config.tmp \
 		$(CONFIG_DIR)/.auto.deps
 
 help:
-- 
1.7.10.4

             reply	other threads:[~2015-05-20  8:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-20  8:45 kaszak at gmail.com [this message]
2015-05-20  9:04 ` [Buildroot] [PATCH] Handle defconfig as .config in .gitignore and distclean Jeremy Rosen
2015-05-20 11:13   ` Károly Kasza
2015-12-27 20:44     ` Yann E. MORIN
2015-12-28  8:20       ` Thomas Petazzoni
2015-12-28 17:24         ` Yann E. MORIN

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=555c49ac.0a64b40a.3499.ffffb3f0@mx.google.com \
    --to=kaszak@gmail.com \
    --cc=buildroot@busybox.net \
    /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