DPDK website maintenance
 help / color / mirror / Atom feed
From: Trishan de Lanerolle <tdelanerolle@linuxfoundation.org>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: web@dpdk.org
Subject: Re: [dpdk-web] Updated charter for upload
Date: Tue, 17 Oct 2017 18:23:38 -0400	[thread overview]
Message-ID: <CAFXL6f9h6tSvP+cErZfC+51Oaj=PWirtsZwUiog0o9YJWtzdeQ@mail.gmail.com> (raw)
In-Reply-To: <1981518.yYJelUI2Ru@xps>

Hi Thomas,
Attached is a version highlighting the specific changes (with tracking)
that should go into the site (note some are updated hyperlinks). Can you
help modify these specific sections along with your formatting and
numbering patches and update the website.

Regards,
Trishan



On Tue, Oct 17, 2017 at 4:24 PM, Thomas Monjalon <thomas@monjalon.net>
wrote:

> Hi,
>
> 17/10/2017 21:16, Trishan de Lanerolle:
> > Hi Thomas,
> > I was trying to compare this to the numbering changes you had in charter
> 2.
> > Had some trouble doing that in Word. Attached is the latest approved
> > charter. Can you help upload this file to the website.
>
> Sorry, I cannot convert a Word document to the HTML version of the charter.
> We use git to bring modifications to the web site (and charter).
>
> Which modification do you want to do?
>
> If it is only about my numbering update, it is available here:
>         http://dpdk.org/about/charter2
> The patches waiting for approval are:
>         http://dpdk.org/ml/archives/web/2017-March/000299.html
>         http://dpdk.org/ml/archives/web/2017-March/000300.html
>
>


-- 
Trishan R. de Lanerolle
Program Manager,  Networking
Linux Foundation
voice: +1.203.699.6401
skype: tdelanerolle
email: tdelanerolle@linuxfoundation.org

  reply	other threads:[~2017-10-17 22:23 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-17 19:16 Trishan de Lanerolle
2017-10-17 20:24 ` Thomas Monjalon
2017-10-17 22:23   ` Trishan de Lanerolle [this message]
2017-10-18 15:04     ` [dpdk-web] [PATCH 0/3] update charter Thomas Monjalon
2017-10-18 15:04       ` [dpdk-web] [PATCH 1/3] update Governing Board responsibilities Thomas Monjalon
2017-10-18 15:26         ` Mcnamara, John
2017-10-18 15:04       ` [dpdk-web] [PATCH 2/3] update Technical Board responsibility wording Thomas Monjalon
2017-10-18 15:26         ` Mcnamara, John
2017-10-18 15:40         ` Dave Neary
2017-10-18 15:41           ` [dpdk-web] [dpdk-govboard] " Dave Neary
2017-10-18 15:04       ` [dpdk-web] [PATCH 3/3] update license policy wording Thomas Monjalon
2017-10-18 15:43         ` [dpdk-web] [dpdk-govboard] " Dave Neary
2017-10-18 15:47         ` [dpdk-web] " Thomas Monjalon
2017-11-28 18:39       ` [dpdk-web] [PATCH v2 0/4] update charter Thomas Monjalon
2017-11-28 18:39         ` [dpdk-web] [PATCH v2 1/4] update Governing Board responsibilities Thomas Monjalon
2017-11-28 18:39         ` [dpdk-web] [PATCH v2 2/4] update Technical " Thomas Monjalon
2017-11-28 18:39         ` [dpdk-web] [PATCH v2 3/4] update license policy wording Thomas Monjalon
2017-11-29  5:34           ` [dpdk-web] [dpdk-govboard] " Hemant Agrawal
2017-11-29  9:25             ` Thomas Monjalon
2017-11-28 18:39         ` [dpdk-web] [PATCH v2 4/4] remove references to Xen dom0 files Thomas Monjalon
2017-12-11 22:09         ` [dpdk-web] [dpdk-techboard] [PATCH v2 0/4] update charter Thomas Monjalon

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='CAFXL6f9h6tSvP+cErZfC+51Oaj=PWirtsZwUiog0o9YJWtzdeQ@mail.gmail.com' \
    --to=tdelanerolle@linuxfoundation.org \
    --cc=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).