From: Linus Torvalds <torvalds@linux-foundation.org>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: Ian Rogers <irogers@google.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] clang-format for v5.7-rc3
Date: Tue, 21 Apr 2020 12:09:46 -0700 [thread overview]
Message-ID: <CAHk-=wiejBvKnrDysDva=DNFgyX02TZred_JMjzUnjFgVOUtOg@mail.gmail.com> (raw)
In-Reply-To: <20200420190916.GA11695@gmail.com>
On Mon, Apr 20, 2020 at 12:09 PM Miguel Ojeda
<miguel.ojeda.sandonis@gmail.com> wrote:
>
> - Don't indent C++ namespaces (Ian Rogers)
I've taken this, since it doesn't matter, but I'm wondering at the
motivation for it (exactly because it shouldn't matter).
Linus
next prev parent reply other threads:[~2020-04-21 19:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 19:09 [GIT PULL] clang-format for v5.7-rc3 Miguel Ojeda
2020-04-21 19:09 ` Linus Torvalds [this message]
2020-04-21 21:03 ` Ian Rogers
2020-04-21 21:16 ` Linus Torvalds
2020-04-21 22:52 ` Miguel Ojeda
2020-04-21 19:40 ` pr-tracker-bot
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='CAHk-=wiejBvKnrDysDva=DNFgyX02TZred_JMjzUnjFgVOUtOg@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=irogers@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miguel.ojeda.sandonis@gmail.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 NNTP newsgroup(s).