DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Butler, Siobhan A" <siobhan.a.butler@intel.com>
To: "Mcnamara, John" <john.mcnamara@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] doc: disable doxygen member sorting
Date: Wed, 29 Apr 2015 13:55:42 +0000	[thread overview]
Message-ID: <0C5AFCA4B3408848ADF2A3073F7D8CC86D5CA360@IRSMSX109.ger.corp.intel.com> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE2F177C8@IRSMSX103.ger.corp.intel.com>

Thanks for making this change John - it helps with readability
Siobhan 

Acked-by Siobhan Butler <siobhan.a.butler@intel.com>

> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Mcnamara, John
> Sent: Wednesday, April 29, 2015 11:52 AM
> To: dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH] doc: disable doxygen member sorting
> 
> > -----Original Message-----
> > From: Mcnamara, John
> > Sent: Wednesday, April 29, 2015 11:48 AM
> > To: dev@dpdk.org
> > Cc: Mcnamara, John
> > Subject: [PATCH] doc: disable doxygen member sorting
> >
> > Disabled the doxygen option to sort member data so that functions and
> > struct memebers are listed in order of definition in the brief and
> > main sections.
> 
> 
> 
> See for example:
> 
>     http://dpdk.org/doc/api/structlcore__config.html
> 
> The first listed member is "unsigned detected" but the first documented
> member is "void* volatile arg".
> 
> John.
> --
> 
> 
> 

  reply	other threads:[~2015-04-29 13:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-29 10:47 John McNamara
2015-04-29 10:51 ` Mcnamara, John
2015-04-29 13:55   ` Butler, Siobhan A [this message]
2015-04-29 15:52     ` Jayakumar, Muthurajan
2015-04-29 16:40     ` Thomas Monjalon

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=0C5AFCA4B3408848ADF2A3073F7D8CC86D5CA360@IRSMSX109.ger.corp.intel.com \
    --to=siobhan.a.butler@intel.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).