DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Iremonger, Bernard" <bernard.iremonger@intel.com>
To: "Richardson, Bruce" <bruce.richardson@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 1/3] docs: change hardcoded date to auto-generated
Date: Wed, 26 Nov 2014 10:38:52 +0000	[thread overview]
Message-ID: <8CEF83825BEC744B83065625E567D7C2049ADD84@IRSMSX107.ger.corp.intel.com> (raw)
In-Reply-To: <1416839034-26652-2-git-send-email-bruce.richardson@intel.com>

> -----Original Message-----
> Subject: [dpdk-dev] [PATCH 1/3] docs: change hardcoded date to auto-generated
> The index.html file for each of the "guide" docs had a hard-coded date value in them of June 2014.
> Rather than update each of these for each revision, just use the |today| directive to insert the date at
> which the document was generated.
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>

Acked-by: Bernard Iremonger <bernard.iremonger@intel.com>

 I have applied the patch to my tree next/dpdk-doc.

  reply	other threads:[~2014-11-26 10:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-24 14:23 [dpdk-dev] [PATCH 0/3] docs: update FreeBSD GSG for 1.8 Bruce Richardson
2014-11-24 14:23 ` [dpdk-dev] [PATCH 1/3] docs: change hardcoded date to auto-generated Bruce Richardson
2014-11-26 10:38   ` Iremonger, Bernard [this message]
2014-11-24 14:43 ` [dpdk-dev] [PATCH 0/3] docs: update FreeBSD GSG for 1.8 Bruce Richardson
2014-11-24 15:25   ` Thomas Monjalon
2014-11-24 15:45     ` Bruce Richardson
2014-11-24 15:48 ` [dpdk-dev] [PATCH 2/3] docs: adjust line lengths in FreeBSD GSG rst files Bruce Richardson
2014-11-26 10:42   ` Iremonger, Bernard
2014-12-03 13:23   ` Thomas Monjalon
2014-12-03 14:54     ` Bruce Richardson
2014-12-04 11:41       ` Iremonger, Bernard
2014-11-24 15:50 ` [dpdk-dev] [PATCH 3/3] docs: update FreeBSD GSG to document ports install Bruce Richardson
2014-11-26 10:44   ` Iremonger, Bernard

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8CEF83825BEC744B83065625E567D7C2049ADD84@IRSMSX107.ger.corp.intel.com \
    --to=bernard.iremonger@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \


* 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).