From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC 3/5] Add NAND SPL entries to gitignore.
Date: Fri, 03 Apr 2009 16:56:57 -0500 [thread overview]
Message-ID: <49D68629.7010003@freescale.com> (raw)
In-Reply-To: <fc034ce887189eafb5ae44597f1786d6b29de08f.1238792177.git.lilja.magnus@gmail.com>
Magnus Lilja wrote:
> diff --git a/nand_spl/.gitignore b/nand_spl/.gitignore
> new file mode 100644
> index 0000000..af5f02b
> --- /dev/null
> +++ b/nand_spl/.gitignore
> @@ -0,0 +1,7 @@
> +# NAND-SPL files
> +/u-boot-spl
> +/u-boot-spl-aligned.bin
> +/u-boot-spl.bin
> +/u-boot-spl.map
> +/board/imx31_phycore/nand_boot_mx31.c
> +/board/imx31_phycore/*.S
Hmm, can we create a directory for board-specific temporary files to go,
so we don't need board-specific stuff in .gitignore?
Or better, add some makefile rules so we can produce nand_spl versions
of .o files without having to symlink the source anywhere.
-Scott
next prev parent reply other threads:[~2009-04-03 21:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-03 21:27 [U-Boot] [RFC 0/5] MX31: NAND boot for phyCORE and PDK boards Magnus Lilja
2009-04-03 21:28 ` [U-Boot] [RFC 1/5] MX31: Add NAND SPL for i.MX31 Magnus Lilja
2009-04-03 21:28 ` [U-Boot] [RFC 2/5] MX31: Add NAND SPL support for phycore i.MX31 board Magnus Lilja
2009-04-03 21:28 ` [U-Boot] [RFC 3/5] Add NAND SPL entries to gitignore Magnus Lilja
2009-04-03 21:28 ` [U-Boot] [RFC 4/5] MX31: Add basic support for Freescale i.MX31 PDK board Magnus Lilja
2009-04-03 21:28 ` [U-Boot] [RFC 5/5] MX31: Add NAND SPL boot support to " Magnus Lilja
2009-04-03 21:56 ` Scott Wood [this message]
2009-04-05 20:35 ` [U-Boot] [RFC 3/5] Add NAND SPL entries to gitignore Magnus Lilja
2009-04-06 18:52 ` Magnus Lilja
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=49D68629.7010003@freescale.com \
--to=scottwood@freescale.com \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.