DPDK website maintenance
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: web@dpdk.org
Subject: [dpdk-web] [PATCH v3 2/5] rename NICs directory
Date: Wed, 21 Nov 2018 01:11:14 +0100	[thread overview]
Message-ID: <20181121001117.24537-3-thomas@monjalon.net> (raw)
In-Reply-To: <20181121001117.24537-1-thomas@monjalon.net>

Lowercase is more common for directories.

Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
---
 content/supported/{NICs => nics}/amazon.md      | 0
 content/supported/{NICs => nics}/atomicrules.md | 0
 content/supported/{NICs => nics}/broadcom.md    | 0
 content/supported/{NICs => nics}/cavium.md      | 0
 content/supported/{NICs => nics}/chelsio.md     | 0
 content/supported/{NICs => nics}/cisco.md       | 0
 content/supported/{NICs => nics}/intel.md       | 0
 content/supported/{NICs => nics}/marvell.md     | 0
 content/supported/{NICs => nics}/mellanox.md    | 0
 content/supported/{NICs => nics}/netcope.md     | 0
 content/supported/{NICs => nics}/netronome.md   | 0
 content/supported/{NICs => nics}/nxp.md         | 0
 content/supported/{NICs => nics}/solarflare.md  | 0
 13 files changed, 0 insertions(+), 0 deletions(-)
 rename content/supported/{NICs => nics}/amazon.md (100%)
 rename content/supported/{NICs => nics}/atomicrules.md (100%)
 rename content/supported/{NICs => nics}/broadcom.md (100%)
 rename content/supported/{NICs => nics}/cavium.md (100%)
 rename content/supported/{NICs => nics}/chelsio.md (100%)
 rename content/supported/{NICs => nics}/cisco.md (100%)
 rename content/supported/{NICs => nics}/intel.md (100%)
 rename content/supported/{NICs => nics}/marvell.md (100%)
 rename content/supported/{NICs => nics}/mellanox.md (100%)
 rename content/supported/{NICs => nics}/netcope.md (100%)
 rename content/supported/{NICs => nics}/netronome.md (100%)
 rename content/supported/{NICs => nics}/nxp.md (100%)
 rename content/supported/{NICs => nics}/solarflare.md (100%)

diff --git a/content/supported/NICs/amazon.md b/content/supported/nics/amazon.md
similarity index 100%
rename from content/supported/NICs/amazon.md
rename to content/supported/nics/amazon.md
diff --git a/content/supported/NICs/atomicrules.md b/content/supported/nics/atomicrules.md
similarity index 100%
rename from content/supported/NICs/atomicrules.md
rename to content/supported/nics/atomicrules.md
diff --git a/content/supported/NICs/broadcom.md b/content/supported/nics/broadcom.md
similarity index 100%
rename from content/supported/NICs/broadcom.md
rename to content/supported/nics/broadcom.md
diff --git a/content/supported/NICs/cavium.md b/content/supported/nics/cavium.md
similarity index 100%
rename from content/supported/NICs/cavium.md
rename to content/supported/nics/cavium.md
diff --git a/content/supported/NICs/chelsio.md b/content/supported/nics/chelsio.md
similarity index 100%
rename from content/supported/NICs/chelsio.md
rename to content/supported/nics/chelsio.md
diff --git a/content/supported/NICs/cisco.md b/content/supported/nics/cisco.md
similarity index 100%
rename from content/supported/NICs/cisco.md
rename to content/supported/nics/cisco.md
diff --git a/content/supported/NICs/intel.md b/content/supported/nics/intel.md
similarity index 100%
rename from content/supported/NICs/intel.md
rename to content/supported/nics/intel.md
diff --git a/content/supported/NICs/marvell.md b/content/supported/nics/marvell.md
similarity index 100%
rename from content/supported/NICs/marvell.md
rename to content/supported/nics/marvell.md
diff --git a/content/supported/NICs/mellanox.md b/content/supported/nics/mellanox.md
similarity index 100%
rename from content/supported/NICs/mellanox.md
rename to content/supported/nics/mellanox.md
diff --git a/content/supported/NICs/netcope.md b/content/supported/nics/netcope.md
similarity index 100%
rename from content/supported/NICs/netcope.md
rename to content/supported/nics/netcope.md
diff --git a/content/supported/NICs/netronome.md b/content/supported/nics/netronome.md
similarity index 100%
rename from content/supported/NICs/netronome.md
rename to content/supported/nics/netronome.md
diff --git a/content/supported/NICs/nxp.md b/content/supported/nics/nxp.md
similarity index 100%
rename from content/supported/NICs/nxp.md
rename to content/supported/nics/nxp.md
diff --git a/content/supported/NICs/solarflare.md b/content/supported/nics/solarflare.md
similarity index 100%
rename from content/supported/NICs/solarflare.md
rename to content/supported/nics/solarflare.md
-- 
2.19.0

  parent reply	other threads:[~2018-11-21  0:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-03 10:14 [dpdk-web] [PATCH v2] add aquantia devices to the list of supported nics Igor Russkikh
2018-11-21  0:11 ` [dpdk-web] [PATCH v3 0/5] clean-up NICs list and add Aquantia Thomas Monjalon
2018-11-21  0:11   ` [dpdk-web] [PATCH v3 1/5] remove useless metadata Thomas Monjalon
2018-11-21  0:11   ` Thomas Monjalon [this message]
2018-11-21  0:11   ` [dpdk-web] [PATCH v3 3/5] simplify NICs list Thomas Monjalon
2018-11-21  0:11   ` [dpdk-web] [PATCH v3 4/5] add driver names in " Thomas Monjalon
2018-11-21  0:11   ` [dpdk-web] [PATCH v3 5/5] add Aquantia devices to supported NICs Thomas Monjalon
2018-11-22 13:55   ` [dpdk-web] [PATCH v3 0/5] clean-up NICs list and add Aquantia Thomas Monjalon
2018-11-22 14:38     ` Ferruh Yigit

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=20181121001117.24537-3-thomas@monjalon.net \
    --to=thomas@monjalon.net \
    --cc=web@dpdk.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).