From: Gaye Abdoulaye Walsimou <walsimou@walsimou.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Add a .gitignore file
Date: Mon, 04 May 2009 10:00:49 +0200 [thread overview]
Message-ID: <49FEA0B1.8050602@walsimou.com> (raw)
In-Reply-To: <49FEE4470200007000014C15@gwia.alliedtelesyn.co.nz>
angus salkeld wrote:
> ---
> .gitignore | 16 ++++++++++++++++
> 1 files changed, 16 insertions(+), 0 deletions(-)
> create mode 100644 .gitignore
>
> diff --git a/.gitignore b/.gitignore
> new file mode 100644
> index 0000000..191e148
> --- /dev/null
> +++ b/.gitignore
> @@ -0,0 +1,16 @@
> +build_*
> +project_*
> +toolchain_*
> +binaries/*
> +.auto.deps
> +.config.cmd
> +.config.old
> +package/config/buildroot-config/
> +package/config/.depend
> +package/config/conf
> +package/config/mconf
> +package/config/*.o
> +package/config/lex.zconf.c
> +package/config/lxdialog/*.o
> +package/config/zconf.hash.c
> +package/config/zconf.tab.c
>
Hello Angus,
I think it is better to add .gitignore file in each subdirectory. So if
a subdirectory comes to be changed, you don't have to modify the
.gitignore file in the root directory, and this avoids having a long
list of ignored files in .gitignore.
Other wise, yes, .gitignore files is a good idea.
Cheers,
next prev parent reply other threads:[~2009-05-04 8:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-04 0:49 [Buildroot] [PATCH] Add a .gitignore file angus salkeld
2009-05-04 8:00 ` Gaye Abdoulaye Walsimou [this message]
2009-05-04 9:04 ` Michael Roth
2009-05-04 19:38 ` angus salkeld
2009-05-04 19:47 ` Peter Korsgaard
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=49FEA0B1.8050602@walsimou.com \
--to=walsimou@walsimou.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