From: Julien Grall <julien.grall@linaro.org>
To: Suriyan Ramasami <suriyan.r@gmail.com>,
Ian Campbell <Ian.Campbell@citrix.com>
Cc: keir@xen.org, Tim Deegan <tim@xen.org>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Jan Beulich <jbeulich@suse.com>,
ian.jackson@citrix.com, Julien Grall <julien.grall@linaro.com>
Subject: Re: [XEN/ARM PATCH v1 1/1] Unbreak Arndale XEN boot
Date: Fri, 12 Sep 2014 11:39:17 -0700 [thread overview]
Message-ID: <54133DD5.9050003@linaro.org> (raw)
In-Reply-To: <CANoR_OBsi0FwGE7kL3j+fvm+3vteZXMkQVn5wVjg=Z3tmwZQuA@mail.gmail.com>
Hi Suriyan,
On 12/09/14 10:50, Suriyan Ramasami wrote:
>> A few procedural comments:
>>
>> Please use "git format-patch" (or even git send-email) and not "git
>> show" to export the patch for sending, this will remove the unnecessary
>> indent.
>>
> I actually use git format-patch to generate the patch, and I do edit
> some of the comments in that patch file, before I use git send-email.
> Can you please give me an example of the "unnecessary indent" that
> you mention, so I can check what I am doing wrong.
Each beginning of your commit message lines start by an indent. git
format-patch should drop it by default.
Current you have smth like:
foo
base
This should be:
foo
base
>
>> The email's subject line will be included into the commit message, so no
>> need to repeat it in the body. "git format-patch" will do the right
>> thing.
>>
>> "Changes between versions" stuff should come after your S-o-b and a
>> "---" (on a line of its own) marker, which means that they won't get
>> included in the commit message.
>>
> Sorry about that. I did know that part (has been repeatedly mentioned
> before). It was a mistake on my part, while editing the output of
> format-patch, I manually copy and paste the version changes that I am
> doing, and this time around I pasted it before the S-o-b. Is that not
> the right approach?
The S-o-b can be generated directly when you generate the commit (git
commit -s ...).
For the changes you can also add in your commit message directly. So you
should not need to modify the patch generated by git format-patch.
Regards,
--
Julien Grall
next prev parent reply other threads:[~2014-09-12 18:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-11 17:25 [XEN/ARM PATCH v1 1/1] Unbreak Arndale XEN boot Suriyan Ramasami
2014-09-11 18:49 ` Julien Grall
2014-09-11 21:01 ` Suriyan Ramasami
2014-09-12 10:08 ` Ian Campbell
2014-09-12 17:50 ` Suriyan Ramasami
2014-09-12 18:39 ` Julien Grall [this message]
2014-09-12 18:47 ` Suriyan Ramasami
2014-09-12 18:58 ` Julien Grall
2014-09-12 19:34 ` Suriyan Ramasami
2014-09-12 21:03 ` Suriyan Ramasami
2014-09-12 21:07 ` Julien Grall
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=54133DD5.9050003@linaro.org \
--to=julien.grall@linaro.org \
--cc=Ian.Campbell@citrix.com \
--cc=ian.jackson@citrix.com \
--cc=jbeulich@suse.com \
--cc=julien.grall@linaro.com \
--cc=keir@xen.org \
--cc=suriyan.r@gmail.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.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).