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
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
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
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.
--
Sent from my mobile device.
On October 14, 2014 2:44:16 AM PDT, 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
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
> >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.
--
Thomas
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.