public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Rebecca Cran" <rebecca@nuviainc.com>
To: Michael Kubacki <mikuback@linux.microsoft.com>, devel@edk2.groups.io
Cc: Leif Lindholm <leif@nuviainc.com>,
	Michael D Kinney <michael.d.kinney@intel.com>,
	Ard Biesheuvel <ardb+tianocore@kernel.org>
Subject: Re: [edk2-devel] Adding *.uncrustify_plugin to .gitignore?
Date: Mon, 13 Dec 2021 08:25:19 -0700	[thread overview]
Message-ID: <abf0516e-84cb-3d56-d5b7-91fec567d2be@nuviainc.com> (raw)
In-Reply-To: <97a6a438-8eb6-2d3d-cb93-46a3e70449f1@linux.microsoft.com>

Sorry, it was operator error: those were obviously left-overs from when 
I was figuring out how to run Uncrustify manually. Now when I run e.g. 
"git ls-files ArmPkg*.c | 
./.pytool/Plugin/Uncrustify/mu-uncrustify-release_extdep/Linux-x86/uncrustify 
-c ./.pytool/Plugin/UncrustifyCheck/uncrustify.cfg -F - --replace 
--no-backup --if-changed" I don't get those files generated.


-- 
Rebecca Cran


On 12/13/21 8:16 AM, Michael Kubacki wrote:
> Hi Rebecca,
>
> Just to make sure everything is working as expected, can you please 
> let me know the scenarios in which you are seeing the files?
>
> Thanks,
> Michael
>
> On 12/12/2021 6:08 PM, Rebecca Cran wrote:
>> I noticed that running Uncrustify results in lots of 
>> .c.uncrustify_plugin files.
>>
>> Should they be added to .gitignore?
>>
>>

  reply	other threads:[~2021-12-13 15:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-12 23:08 Adding *.uncrustify_plugin to .gitignore? Rebecca Cran
2021-12-13 15:16 ` [edk2-devel] " Michael Kubacki
2021-12-13 15:25   ` Rebecca Cran [this message]
2021-12-13 18:20     ` Michael Kubacki

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-list 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=abf0516e-84cb-3d56-d5b7-91fec567d2be@nuviainc.com \
    --to=devel@edk2.groups.io \
    /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