From: Matthew Hall <mhall@mhcomputing.net>
To: Stephen Hemminger <stephen@networkplumber.org>,
Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] virtio-net-pmd: .gitignore: ignore librte_pmd_virtio.so
Date: Tue, 14 Oct 2014 08:40:20 -0700 [thread overview]
Message-ID: <A543BD8D-4DAB-45F0-8C92-6413E88B7ADB@mhcomputing.net> (raw)
In-Reply-To: <20141014115220.5c9ba581@uryu.home.lan>
Sure, I can put the classic C gitignore entries in there if you guys prefer. I was just trying to make the minimum change to get it to work right for my environment.
--
Sent from my mobile device.
On October 14, 2014 2:52:20 AM PDT, Stephen Hemminger <stephen@networkplumber.org> wrote:
>On Tue, 14 Oct 2014 10:44:16 +0100
>Bruce Richardson <bruce.richardson@intel.com> wrote:
>
>> On Tue, Oct 14, 2014 at 07:53:56AM +0000, Matthew Hall wrote:
>> > Signed-off-by: Matthew Hall <mhall@mhcomputing.net>
>> > ---
>> > .gitignore | 1 +
>> > 1 file changed, 1 insertion(+)
>> >
>> > diff --git a/.gitignore b/.gitignore
>> > index e69de29..08d831a 100644
>> > --- a/.gitignore
>> > +++ b/.gitignore
>> > @@ -0,0 +1 @@
>> > +librte_pmd_virtio.so
>> > --
>> > 1.9.1
>> >
>>
>> 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
>
>Why not add *.so to ignore all built shared libraries
next prev parent reply other threads:[~2014-10-14 15:32 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 [this message]
2014-10-14 15:38 ` Matthew Hall
2014-10-14 16:09 ` Thomas Monjalon
2014-10-14 16:12 ` Matthew Hall
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=A543BD8D-4DAB-45F0-8C92-6413E88B7ADB@mhcomputing.net \
--to=mhall@mhcomputing.net \
--cc=bruce.richardson@intel.com \
--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).