From: Thomas Monjalon <thomas@monjalon.net>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] git: ignore build directory
Date: Tue, 22 May 2018 23:42:19 +0200 [thread overview]
Message-ID: <1674231.4QnvL2R4ds@xps> (raw)
In-Reply-To: <1458582978-19813-1-git-send-email-stephen@networkplumber.org>
21/03/2016 18:56, Stephen Hemminger:
> The mk environment in DPDK puts files in build/ directory
> so it makes sense to have a .gitignore file to skip that
> directory.
>
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> ---
> .gitignore | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/.gitignore b/.gitignore
> index e69de29..5dc652b 100644
> --- a/.gitignore
> +++ b/.gitignore
> @@ -0,0 +1,5 @@
> +*.orig
> +*.rej
> +*~
> +
> +build
Seems I never replied to this proposal.
I think .orig, .rej and other files should appear in git status.
About the "build" directory, yes it could be ignored.
But then we could ignore the default build directory and not other
build directories with specific names? Looks not consistent.
prev parent reply other threads:[~2018-05-22 21:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-21 17:56 Stephen Hemminger
2016-03-21 20:57 ` Matthew Hall
2018-05-22 21:42 ` Thomas Monjalon [this message]
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=1674231.4QnvL2R4ds@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).