DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Butler, Siobhan A" <siobhan.a.butler@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] proposal: remove separate doc tree
Date: Wed, 04 Mar 2015 13:06:34 -0800 (PST)	[thread overview]
Message-ID: <1493075.lJ5R1HNxeh@xps13> (raw)
In-Reply-To: <0C5AFCA4B3408848ADF2A3073F7D8CC86D4DBF3A@IRSMSX109.ger.corp.intel.com>

2015-02-11 14:28, Butler, Siobhan A:
> Hi all,
> 
> In creating documentation for DPDK 1.8.0 dpdk.org used a separate repository 'dpdk-doc' to work on the conversion of old documentation from PDF to .rst with sphinx for maintainability and usability purposes.
> Now that the conversion has been complete and patches to the documentation can be made, I propose that we no longer need the additional repo and it should be removed.
> 
> Many Thanks,
> Siobhan Butler

OK, it's now removed.
Thanks

  reply	other threads:[~2015-03-04 21:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-11 14:28 Butler, Siobhan A
2015-03-04 21:06 ` Thomas Monjalon [this message]
2015-03-05  8:19   ` Butler, Siobhan A

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=1493075.lJ5R1HNxeh@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=siobhan.a.butler@intel.com \
    /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).