From: "Ard Biesheuvel" <ardb@kernel.org>
To: devel@edk2.groups.io, osteffen@redhat.com
Cc: Rebecca Cran <rebecca@bsdio.com>,
mikuback@linux.microsoft.com, Andrew Fish <afish@apple.com>,
Chris Fernald <chris.fernald@outlook.com>,
Leif Lindholm <quic_llindhol@quicinc.com>,
Michael D Kinney <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] [PATCH v1 1/1] .devcontainer/devcontainer.json: Add devcontainer file
Date: Mon, 23 Jan 2023 11:46:54 +0100 [thread overview]
Message-ID: <CAMj1kXHK3Xq9YVe+AXuunFfEriZWn=EJt0nWiwXJMMPW7Rg2yg@mail.gmail.com> (raw)
In-Reply-To: <CA+bRGFr8C0_cRz5B8vKXHVVu9aGKfO7RSEmOCy6TARuS8-P7BQ@mail.gmail.com>
On Mon, 23 Jan 2023 at 10:23, Oliver Steffen <osteffen@redhat.com> wrote:
>
> Quoting Rebecca Cran (2023-01-20 22:22:55)
> > Related to this, I've been wondering if we might want to commit a .vscode directory with project configuration file(s)?
>
> As long as project settings for other IDEs (should
> there be a reasonable user base) would be accepted in the future, why not?
>
> >
> > Also perhaps a .editorconfig file?
> I like the idea, because it is understood by many IDEs and text editors.
>
Yes, please, this would be very useful.
next prev parent reply other threads:[~2023-01-23 10:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-20 20:51 [PATCH v1 1/1] .devcontainer/devcontainer.json: Add devcontainer file Michael Kubacki
2023-01-20 21:22 ` [edk2-devel] " Rebecca Cran
2023-01-20 21:57 ` Michael Kubacki
2023-01-23 9:23 ` Oliver Steffen
2023-01-23 10:46 ` Ard Biesheuvel [this message]
[not found] <173C1FA3C96CC3CD.14781@groups.io>
2023-01-20 20:54 ` Michael Kubacki
2023-01-24 9:52 ` Oliver Steffen
2023-01-26 14:44 ` Michael Kubacki
[not found] ` <173DE310BC2140E3.21537@groups.io>
2023-02-05 18:34 ` Michael Kubacki
2023-02-05 19:54 ` Michael D Kinney
2023-02-08 3:49 ` Michael Kubacki
2023-02-10 5:01 ` Michael D Kinney
2023-02-13 14:13 ` Michael Kubacki
2023-02-14 1:28 ` Michael D Kinney
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='CAMj1kXHK3Xq9YVe+AXuunFfEriZWn=EJt0nWiwXJMMPW7Rg2yg@mail.gmail.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