DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org, Stephen Hemminger <stephen@networkplumber.org>,
	Rami Rosen <ramirose@gmail.com>
Subject: Re: [dpdk-dev] [PATCH v2 1/4] .gitignore: add section header comments
Date: Wed, 13 Mar 2019 11:57:44 +0100	[thread overview]
Message-ID: <4328758.3e5kqPkfLo@xps> (raw)
In-Reply-To: <20190311105732.24121-1-bruce.richardson@intel.com>

11/03/2019 11:57, Bruce Richardson:
> Split the ignored file list into section based on logical groups of files,
> putting a comment at the top of each section clarifying what it is.
> 
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>

Series applied, thanks

      parent reply	other threads:[~2019-03-13 10:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-06 17:05 [dpdk-dev] [PATCH " Bruce Richardson
2019-03-06 17:05 ` [dpdk-dev] [PATCH 2/4] .gitignore: ignore python bytecode files Bruce Richardson
2019-03-06 17:05 ` [dpdk-dev] [PATCH 3/4] .gitignore: ignore hidden files Bruce Richardson
2019-03-06 17:05 ` [dpdk-dev] [PATCH 4/4] .gitignore: ignore build directories from test-meson-build Bruce Richardson
2019-03-09  0:47   ` Thomas Monjalon
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 ` [dpdk-dev] [PATCH v2 1/4] .gitignore: add section header comments Bruce Richardson
2019-03-11 10:57   ` [dpdk-dev] [PATCH v2 2/4] .gitignore: ignore python bytecode files Bruce Richardson
2019-03-11 10:57   ` [dpdk-dev] [PATCH v2 3/4] .gitignore: ignore hidden files Bruce Richardson
2019-03-11 10:57   ` [dpdk-dev] [PATCH v2 4/4] .gitignore: ignore build directories Bruce Richardson
2019-03-11 17:27     ` Rami Rosen
2019-03-13 10:57   ` 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=4328758.3e5kqPkfLo@xps \
    --to=thomas@monjalon.net \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=ramirose@gmail.com \
    --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).