DPDK website maintenance
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
Cc: Ferruh Yigit <ferruh.yigit@intel.com>, dpdk-web <web@dpdk.org>,
	dpdk-spp <spp@dpdk.org>
Subject: Re: [dpdk-web] SPP documentation update on dpdk.org
Date: Mon, 17 Dec 2018 10:42:37 +0100	[thread overview]
Message-ID: <2007463.DxDJOrdxxc@xps> (raw)
In-Reply-To: <a1125dea-61ed-1980-bd44-8804bdfcf5d0@lab.ntt.co.jp>

17/12/2018 08:33, Yasufumi Ogawa:
> >>> Last but not the least, the doc will be generated only when you push an annotated tag:
> >>> 	git tag -am spp-18.08 v18.08
> >> I understand pushing tag is also incorrect. I simply added the tag and pushed.
> >>     $ git tag v18.08
> >>     $ git push origin v18.08
> > 
> > This does not trigger compilation of the doc.
> > You must use *annotated* tags.
> Hi Thomas,
> 
> I tried to add annotated tag for v18.08.1 and push to the repository after applied your patch. However, it does not seem to be 
> working. I confirmed the version number is defined in GNUmakefile as 'VERSION := 18.08.1', and added annotated tag. Here is a 
> result of 'git show' in which annotation is found. Could you give me advice?

It is a bug in the script stripping the minor version number.
I fixed it and ran the script again.

  reply	other threads:[~2018-12-17  9:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-10 11:26 Ferruh Yigit
2018-12-10 16:52 ` Yasufumi Ogawa
2018-12-11  6:42   ` Thomas Monjalon
2018-12-12  6:22     ` Yasufumi Ogawa
2018-12-12 10:17       ` Thomas Monjalon
2018-12-12 19:18         ` Yasufumi Ogawa
2018-12-17  7:33         ` Yasufumi Ogawa
2018-12-17  9:42           ` Thomas Monjalon [this message]
2018-12-17 10:03             ` Yasufumi Ogawa

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=2007463.DxDJOrdxxc@xps \
    --to=thomas@monjalon.net \
    --cc=ferruh.yigit@intel.com \
    --cc=ogawa.yasufumi@lab.ntt.co.jp \
    --cc=spp@dpdk.org \
    --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).