From: Laurence Withers <lwithers@guralp.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ignore soc asm-offsets.s
Date: Thu, 29 Sep 2011 12:40:33 +0000 [thread overview]
Message-ID: <20110929124033.GG10893@guralp.com> (raw)
In-Reply-To: <1315802844-24604-1-git-send-email-vapier@gentoo.org>
On Mon, Sep 12, 2011 at 12:47:24AM -0400, Mike Frysinger wrote:
> Recent commit a4814a69d3bca6ee05f4bfc4 cleaned up generation of
> asm-offsets.s for SoC dirs, but missed adding it to the ignore
> list which makes it show up in `git status`.
>
> Signed-off-by: Mike Frysinger <vapier@gentoo.org>
> ---
> .gitignore | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/.gitignore b/.gitignore
> index dbf545f..2a82cd9 100644
> --- a/.gitignore
> +++ b/.gitignore
> @@ -46,6 +46,7 @@
>
> /include/generated/
> /lib/asm-offsets.s
> +/arch/*/cpu/asm-offsets.s
>
> # stgit generated dirs
> patches-*
Dear Mike,
There appear to be some SoCs which have further subdirectories, e.g.:
lwithers at rhodium u-boot $ git status
# On branch lw-diamond
# Untracked files:
# (use "git add <file>..." to include in what will be committed)
#
# arch/arm/cpu/arm926ejs/davinci/asm-offsets.s
nothing added to commit but untracked files present (use "git add" to track)
We could ignore all files named asm-offsets.s , or perhaps all files under
arch ?
Bye for now,
--
Laurence Withers, <lwithers@guralp.com> http://www.guralp.com/
Direct tel:+447753988197 or tel:+443333408643 Software Engineer
General support queries: <support@guralp.com> CMG-DCM CMG-EAM CMG-NAM
next prev parent reply other threads:[~2011-09-29 12:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-12 4:47 [U-Boot] [PATCH] ignore soc asm-offsets.s Mike Frysinger
2011-09-21 21:02 ` Wolfgang Denk
2011-09-29 12:40 ` Laurence Withers [this message]
2011-09-29 14:30 ` Mike Frysinger
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=20110929124033.GG10893@guralp.com \
--to=lwithers@guralp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox