From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>, dev@dpdk.org
Subject: Re: [dpdk-dev] Editor Config
Date: Fri, 26 Apr 2019 09:13:43 +0100 [thread overview]
Message-ID: <44cac678-9e3c-bb93-7451-88a13b801d79@intel.com> (raw)
Message-ID: <20190426081343.Mxm28mp5xg5dwW9I2I5_ViiYRGdZjtTXfi4Lg6v9Dog@z> (raw)
In-Reply-To: <20190425101944.72132e0a@hermes.lan>
On 25-Apr-19 6:19 PM, Stephen Hemminger wrote:
> Systemd uses this and it looks like a useful addition to the DPDK source
> base. Especially since we now have Windows developers.
>
> https://editorconfig.org/
>
I have suggested using clang-format in the past, but this would be a
good step too.
--
Thanks,
Anatoly
next prev parent reply other threads:[~2019-04-26 8:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-25 17:19 Stephen Hemminger
2019-04-25 17:19 ` Stephen Hemminger
2019-04-26 8:13 ` Burakov, Anatoly [this message]
2019-04-26 8:13 ` Burakov, Anatoly
2019-04-26 12:50 ` Wiles, Keith
2019-04-26 12:50 ` Wiles, Keith
2019-04-29 9:58 ` Ray Kinsella
2019-04-29 9:58 ` Ray Kinsella
2019-04-26 8:24 ` Andrew Rybchenko
2019-04-26 8:24 ` Andrew Rybchenko
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=44cac678-9e3c-bb93-7451-88a13b801d79@intel.com \
--to=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.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).