From: Tom Rix <tom@bumblecow.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] update include/asm/ gitignore after move
Date: Mon, 03 May 2010 07:25:44 -0500 [thread overview]
Message-ID: <4BDEC0C8.3040206@bumblecow.com> (raw)
In-Reply-To: <1272392134-13368-2-git-send-email-vapier@gentoo.org>
Mike Frysinger wrote:
> With the cpu include paths moved, the gitignore paths need updating.
>
> Signed-off-by: Mike Frysinger <vapier@gentoo.org>
This looks fine.
Old :
> git status
# On branch blablabla
# Untracked files:
# (use "git add <file>..." to include in what will be committed)
#
# arch/arm/include/asm/arch
# arch/arm/include/asm/proc
nothing added to commit but untracked files present (use "git add" to track)
New :
> git status
# On branch blablabla
# Your branch is ahead of 'origin/master' by 1 commit.
#
nothing to commit (working directory clean)
Tested-by Tom Rix <tom@bumblecow.com>
> ---
> arch/.gitignore | 2 ++
> include/.gitignore | 2 --
> 2 files changed, 2 insertions(+), 2 deletions(-)
> create mode 100644 arch/.gitignore
>
> diff --git a/arch/.gitignore b/arch/.gitignore
> new file mode 100644
> index 0000000..a1fbe01
> --- /dev/null
> +++ b/arch/.gitignore
> @@ -0,0 +1,2 @@
> +/*/include/asm/arch
> +/*/include/asm/proc
> diff --git a/include/.gitignore b/include/.gitignore
> index 4481412..77594e5 100644
> --- a/include/.gitignore
> +++ b/include/.gitignore
> @@ -1,7 +1,5 @@
> /autoconf.mk*
> /asm
> -/asm-*/arch
> -/asm-*/proc
> /bmp_logo.h
> /config.h
> /config.mk
next prev parent reply other threads:[~2010-05-03 12:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-27 18:15 [U-Boot] [PATCH] update include/asm/ gitignore after move Mike Frysinger
2010-04-27 18:15 ` Mike Frysinger
2010-05-03 12:25 ` Tom Rix [this message]
2010-05-06 22:17 ` Wolfgang Denk
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=4BDEC0C8.3040206@bumblecow.com \
--to=tom@bumblecow.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