DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Mcnamara, John" <john.mcnamara@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v1] doc: add template release notes for 17.05
Date: Fri, 17 Feb 2017 11:07:19 +0100	[thread overview]
Message-ID: <2388353.BO9j0tXAKD@xps13> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE2026CFEC0@IRSMSX103.ger.corp.intel.com>

2017-02-16 15:01, Mcnamara, John:
> 
> > -----Original Message-----
> > From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> > Sent: Wednesday, February 15, 2017 2:55 PM
> > To: Mcnamara, John <john.mcnamara@intel.com>
> > Cc: dev@dpdk.org
> > Subject: Re: [dpdk-dev] [PATCH v1] doc: add template release notes for
> > 17.05
> > 
> > 2017-02-15 12:38, John McNamara:
> > > +   Build the docs and view the output file to ensure the changes are
> > correct::
> > > +
> > > +      make doc-guides-html
> > > +
> > > +      firefox build/doc/html/guides/rel_notes/release_17_05.html
> > 
> > I would suggest xdg-open instead of firefox.
> > It is more open regarding chromium ;)
> 
> I generally use xdg-open, which in my case gives me midori but for the
> docs it is probably better to have something that is easily recognizable
> as a browser. Either way I'm okay if you wish to make the change inline
> during merge. Or would you prefer a V2.

Midori? Seems another interesting choice:)

Applied with this change, thanks

      reply	other threads:[~2017-02-17 10:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-15 12:38 John McNamara
2017-02-15 14:01 ` Bruce Richardson
2017-02-15 14:54 ` Thomas Monjalon
2017-02-16 15:01   ` Mcnamara, John
2017-02-17 10:07     ` Thomas Monjalon [this message]

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=2388353.BO9j0tXAKD@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@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).