From: Simon Marchi <simon.marchi@polymtl.ca>
To: Nick Clifton <nickc@redhat.com>,
gdb-patches@sourceware.org, binutils@sourceware.org
Subject: Re: [PATCH] Add top-level .editorconfig file
Date: Fri, 28 Jan 2022 08:25:15 -0500 [thread overview]
Message-ID: <b03dacf0-fe4b-4765-404e-df069f4bd6d3@polymtl.ca> (raw)
In-Reply-To: <cf83593b-afd5-51cf-0bd1-54d36f7de64b@redhat.com>
On 2022-01-28 08:03, Nick Clifton wrote:
> Hi Simon,
>
>> Good idea, I will add this comment at the top:
>>
>> # This file helps editors auto-configure whitespace settings.
>> #
>> # See here for more information about the format and editor support:
>> #
>> # https://editorconfig.org/
>
> In which case if you are still looking for an approval, then please
> consider the patch approved.
>
> Cheers
> Nick
Thanks Nick, will merge.
Simon
prev parent reply other threads:[~2022-01-28 13:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 20:15 Simon Marchi
2022-01-28 11:57 ` Nick Clifton
2022-01-28 12:26 ` Simon Marchi
2022-01-28 13:03 ` Nick Clifton
2022-01-28 13:25 ` Simon Marchi [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=b03dacf0-fe4b-4765-404e-df069f4bd6d3@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=nickc@redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).