From: Matthew Hall <mhall@mhcomputing.net>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] virtio-net-pmd: .gitignore: ignore librte_pmd_virtio.so
Date: Tue, 14 Oct 2014 09:12:35 -0700 [thread overview]
Message-ID: <DA4E51A6-B7A5-41A2-9565-2B294242E547@mhcomputing.net> (raw)
In-Reply-To: <3422655.1tIybTbukh@xps13>
In the virtio-net-pmd it is done in the same directory. Hence me submitting this to try to make it easier for others to use the product.
Also the default DPDK doesn't ignore the build target directories... but I already had to fork that one to fix clang compile failures in the examples files.
Matthew.
--
Sent from my mobile device.
On October 14, 2014 9:09:49 AM PDT, Thomas Monjalon <thomas.monjalon@6wind.com> wrote:
>> >I thought our .gitignore could do with a few entries added alright,
>I
>> >just never expected this one to be top of the list! While I don't
>think
>> >it does any harm, I'm just curious why you think it needs to be
>added?
>> >
>> >/Bruce
>>
>> I import all my DPDK dependencies as git submodules. When the
>submodules
>> contain unignored files, they get marked as dirty by git, and it
>makes
>> like difficult when it comes to updating my submodule pointers.
>>
>> Matthew.
>
>So you cannot update submodules without filling .gitignore?
>
>I'm not a big fan of .gitignore because I like seeing what has been
>generated by looking at "git status".
>And it's not really needed in DPDK because compilation is often done in
>a separate directory.
prev parent reply other threads:[~2014-10-14 16:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-14 7:53 Matthew Hall
2014-10-14 9:44 ` Bruce Richardson
2014-10-14 9:52 ` Stephen Hemminger
2014-10-14 15:40 ` Matthew Hall
2014-10-14 15:38 ` Matthew Hall
2014-10-14 16:09 ` Thomas Monjalon
2014-10-14 16:12 ` Matthew Hall [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=DA4E51A6-B7A5-41A2-9565-2B294242E547@mhcomputing.net \
--to=mhall@mhcomputing.net \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.com \
/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).