From: Thomas Monjalon <thomas@monjalon.net>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH 4/4] .gitignore: ignore build directories from test-meson-build
Date: Sat, 09 Mar 2019 01:47:32 +0100 [thread overview]
Message-ID: <1735146.Ys0eitMVbl@xps> (raw)
In-Reply-To: <20190306170557.65627-4-bruce.richardson@intel.com>
06/03/2019 18:05, Bruce Richardson:
> test-meson-build.sh generates multiple build directories for various
> targets. As these follow a few known patterns of reasonable lengths,
> and since they don't need to be tracked in git, we can add them to
> the gitignore file.
>
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> ---
> --- a/.gitignore
> +++ b/.gitignore
> +build-arm64-*
> +build-clang-*
> +build-gcc-*
> +build-x86-default
We could even ignore build-* ?
next prev parent reply other threads:[~2019-03-09 0:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-06 17:05 [PATCH 1/4] .gitignore: add section header comments Bruce Richardson
2019-03-06 17:05 ` [PATCH 2/4] .gitignore: ignore python bytecode files Bruce Richardson
2019-03-06 17:05 ` [PATCH 3/4] .gitignore: ignore hidden files Bruce Richardson
2019-03-06 17:05 ` [PATCH 4/4] .gitignore: ignore build directories from test-meson-build Bruce Richardson
2019-03-09 0:47 ` Thomas Monjalon [this message]
2019-03-09 3:03 ` Stephen Hemminger
2019-03-09 10:40 ` Thomas Monjalon
2019-03-09 13:32 ` Rami Rosen
2019-03-11 9:46 ` Bruce Richardson
2019-03-11 10:57 ` [PATCH v2 1/4] .gitignore: add section header comments Bruce Richardson
2019-03-11 10:57 ` [PATCH v2 2/4] .gitignore: ignore python bytecode files Bruce Richardson
2019-03-11 10:57 ` [PATCH v2 3/4] .gitignore: ignore hidden files Bruce Richardson
2019-03-11 10:57 ` [PATCH v2 4/4] .gitignore: ignore build directories Bruce Richardson
2019-03-11 17:27 ` Rami Rosen
2019-03-13 10:57 ` [PATCH v2 1/4] .gitignore: add section header comments Thomas Monjalon
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=1735146.Ys0eitMVbl@xps \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
/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.