From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "thomas@monjalon.net" <thomas@monjalon.net>,
"web@dpdk.org" <web@dpdk.org>
Cc: "dts@dpdk.org" <dts@dpdk.org>
Subject: [dpdk-web] DTS documentation update on dpdk.org
Date: Tue, 11 Dec 2018 07:56:34 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0B9DED7F@SHSMSX101.ccr.corp.intel.com> (raw)
Hi Thomas,
Can I ask how it is to trigger the DTS document update on dpdk.org?
I checked the doc build locally, and there is no build errors, then I make the DTS tag using "git tag -a 18.11".
I supposed the DTS document will be updated automatically, but actually I find still the old document on web pages.
http://doc.dpdk.org/dts/gsg/
http://doc.dpdk.org/dts/test_plans/
thanks,
Lijuan.
next reply other threads:[~2018-12-11 7:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-11 7:56 Tu, Lijuan [this message]
2018-12-11 9:15 ` Thomas Monjalon
2018-12-11 11:22 ` Tu, Lijuan
2018-12-13 10:51 ` Tu, Lijuan
2018-12-13 13:40 ` Thomas Monjalon
2018-12-14 1:30 ` Tu, Lijuan
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=8CE3E05A3F976642AAB0F4675D0AD20E0B9DED7F@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.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).