From: Sean Christopherson <seanjc@google.com>
To: Jun Miao <jun.miao@intel.com>
Cc: pbonzini@redhat.com, kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KVM: Align two spacebar after period key in annotation
Date: Mon, 10 Oct 2022 19:10:11 +0000 [thread overview]
Message-ID: <Y0RuE2fDAkjVpZE1@google.com> (raw)
In-Reply-To: <20221010074052.72197-1-jun.miao@intel.com>
On Mon, Oct 10, 2022, Jun Miao wrote:
> After you hit the period key, you'd hit the spacebar twice in a line.
> A little change in annotation does not affect code.
I'm a firm believer in two spaces after a period and think one-spacers are
misguided heathens, but I'd prefer not to fix up existing comments. IMO the potential
for unnecessary conflicts with in-flight development isn't worth the almost negligible
benefits. And unless checkpatch complains about using a single space, which it
currently does not, there's zero chance we'll be able to enforce this the preferred
KVM style.
prev parent reply other threads:[~2022-10-10 19:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-10 7:40 [PATCH] KVM: Align two spacebar after period key in annotation Jun Miao
2022-10-10 19:10 ` Sean Christopherson [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=Y0RuE2fDAkjVpZE1@google.com \
--to=seanjc@google.com \
--cc=jun.miao@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@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