DPDK patches and discussions
 help / color / mirror / Atom feed
From: Matthew Hall <mhall@mhcomputing.net>
To: dev@dpdk.org
Subject: Re: [dpdk-dev] OK to reindent the pktgen (mix of tabs and spaces, etc.)?
Date: Sun, 3 Jan 2016 00:06:28 -0800	[thread overview]
Message-ID: <5688D684.2070107@mhcomputing.net> (raw)
In-Reply-To: <20151123071037.GA1771@mhcomputing.net>

Hello,

In over a month I didn't get a reply if it would be OK to clean up the 
inconsistent tabs and spaces indents in the pktgen, to make it easier 
for the community to read the code and help maintain it and add bug fixes.

It would be very helpful if I could get a response and a plan for this 
if my proposal is not acceptable, or it's not going to be very pleasant 
to patch any bugs I find when testing it, as some of the stuff I'd want 
to work on in the pktgen comes from files with weird indentation that is 
not consistent and thus painful to send patches.

Sincerely,
Matthew.

On 11/22/15 11:10 PM, Matthew Hall wrote:
> I would like to reindent it using the following astyle command, with a few
> small hand edits past that level, to get it closer to most other DPDK code as
> the inconsistent mix of tabs, spaces, etc. makes it difficult to read and
> debug when it has issues.
>
> Obviously the upstream Lua and common/wr_* code would not be included as they
> seem to be copied from elsewhere w/ different upstream standards.
>
> If I were to make the big diff needed for this, would this item be acceptable
> upstream?
>
> Otherwise it is going to be hard to get more people working on the code
> reliably as it will be hard for others to follow besides the original authors.
>
> astyle \
> --max-code-length=132 \
> --style=attach \
> --break-closing-brackets \
> --add-brackets \
> --indent=force-tab=8 \
> --indent-switches \
> --indent-labels \
> --indent-col1-comments \
> --pad-oper \
> --pad-header \
> --unpad-paren \
> --align-pointer=type \
> --align-reference=type \
> --suffix=none \
> --lineend=linux \
> ./app/**/*.{c,h}
>
> Sincerely,
> Matthew.
>

      reply	other threads:[~2016-01-03  8:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-23  7:10 Matthew Hall
2016-01-03  8:06 ` Matthew Hall [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=5688D684.2070107@mhcomputing.net \
    --to=mhall@mhcomputing.net \
    --cc=dev@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).