From: lijuan.tu@intel.com
To: dts@dpdk.org,ohilyard@iol.unh.edu
Cc: lijuan.tu@intel.com,Owen Hilyard <ohilyard@iol.unh.edu>
Subject: [PATCH v1] ci/check_formatting: Added a script to check formatting
Date: 06 Apr 2022 05:48:49 -0700 [thread overview]
Message-ID: <722c05$gc2a2h@orsmga007-auth.jf.intel.com> (raw)
In-Reply-To: <20220331203743.14365-1-ohilyard@iol.unh.edu>
On Thu, 31 Mar 2022 16:37:44 -0400, ohilyard@iol.unh.edu wrote:
> From: Owen Hilyard <ohilyard@iol.unh.edu>
>
> The script should be run from the repository root. It will exit with
> exit code 0 if everything is properly formatted. It will exit with exit
> code 1 if formatting happened. It will also print a git shortstat diff,
> which will display all of the incorrectly formatted files.
>
> Signed-off-by: Owen Hilyard <ohilyard@iol.unh.edu>
Applied, thanks
prev parent reply other threads:[~2022-04-06 12:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-31 20:37 ohilyard
2022-04-06 12:48 ` lijuan.tu [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='722c05$gc2a2h@orsmga007-auth.jf.intel.com' \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=ohilyard@iol.unh.edu \
/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).