public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Marcin Juszkiewicz" <marcin.juszkiewicz@linaro.org>
To: Pedro Falcato <pedro.falcato@gmail.com>, devel@edk2.groups.io
Subject: Re: [edk2-devel] Maybe it is time to update code style?
Date: Mon, 25 Sep 2023 21:22:36 +0200	[thread overview]
Message-ID: <bd4bde62-ca78-4cff-9619-41d6bda74d75@linaro.org> (raw)
In-Reply-To: <CAKbZUD2m3uFgXu31J2Dhbzsnm1KBbCSuMuq-yduw+AB-PmgSAg@mail.gmail.com>

W dniu 25.09.2023 o 20:03, Pedro Falcato pisze:
> On Mon, Sep 25, 2023 at 10:03 AM Marcin Juszkiewicz

>> And can someone take a look at config of code obfuscator used for linting?
>> It spits out amount of information showing that noone looked at updating it
>> to current version:
> 
> You're supposed to use the edk2 uncrustify fork that you get *somehow*
> (no, I don't remember how, I do remember it was a pain though).

If it is not latest upstream then maybe it should be merged into 
BaseTools and kept there?

> But seriously, speaking as someone with a completely different
> personal coding style, the coding style really isn't all that bad (at
> the very least, it's tolerable), it's just a bastardized NT-kernel
> style, and with uncrustify you can auto-format all your code.

When it works and do not complain about own config.

> What really pains me is CRLF vs LF, which breaks *every git tool*.
> Seriously, applying patches tends to be a pain, at least on Linux.

Argh. That's pain in the ass. I handle most of (outside of ML) sharing 
patches via own fork repo as it is easier than git format-patch+am combo.



-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#109049): https://edk2.groups.io/g/devel/message/109049
Mute This Topic: https://groups.io/mt/101570674/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



      reply	other threads:[~2023-09-25 19:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-25  9:03 [edk2-devel] Maybe it is time to update code style? Marcin Juszkiewicz
2023-09-25 15:25 ` Michael D Kinney
2023-09-25 15:39 ` Andrew Fish via groups.io
2023-09-25 17:16 ` Rebecca Cran via groups.io
2023-09-25 18:03 ` Pedro Falcato
2023-09-25 19:22   ` Marcin Juszkiewicz [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-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=bd4bde62-ca78-4cff-9619-41d6bda74d75@linaro.org \
    --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