From: Peter Maydell <peter.maydell@linaro.org>
To: Sergey Sorokin <afarallax@yandex.ru>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] target-arm: Fix general-purpose register mapping between AArch32 state and AArch64 state
Date: Wed, 2 Sep 2015 11:41:49 +0100 [thread overview]
Message-ID: <CAFEAcA_yus_Og3VSOs0pOqs6hW6o2HTgRfeEDcHDKz3TxzDAPQ@mail.gmail.com> (raw)
In-Reply-To: <1068401441187583@web21j.yandex.ru>
On 2 September 2015 at 10:53, Sergey Sorokin <afarallax@yandex.ru> wrote:
> I did so. As I see, the longest line in the message is 78 chars.
> How short should it be in the patches?
If you look at the output of "git log" you'll see that git formats
the commit messages with a four-character left margin. So you need
to keep them short enough that they don't overflow when indented a
bit -- 70..75 chars is probably about as wide as you want.
thanks
-- PMM
prev parent reply other threads:[~2015-09-02 10:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-28 21:14 [Qemu-devel] [PATCH] target-arm: Fix general-purpose register mapping between AArch32 state and AArch64 state Sergey Sorokin
2015-09-01 16:56 ` Peter Maydell
2015-09-02 9:53 ` Sergey Sorokin
2015-09-02 10:41 ` Peter Maydell [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=CAFEAcA_yus_Og3VSOs0pOqs6hW6o2HTgRfeEDcHDKz3TxzDAPQ@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=afarallax@yandex.ru \
--cc=qemu-devel@nongnu.org \
/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).