From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] arm-soc: Xilinx zynq changes for v3.8
Date: Fri, 16 Nov 2012 17:46:15 +0000 [thread overview]
Message-ID: <201211161746.15629.arnd@arndb.de> (raw)
In-Reply-To: <52241ede-3d28-43fc-967d-36ab64d52592@CH1EHSMHS038.ehs.local>
On Friday 16 November 2012, Michal Simek wrote:
> > * Please provide a description of the series that I can put into the merge
> > changeset, either in the introductory mail or (better) into the signed tag that
> > you send (git tag -s). Have a look at how Tony Lindgren does this, he writes the
> > best descriptions.
>
> No. Do you have a link?
See for example http://www.spinics.net/lists/arm-kernel/msg207098.html
This is a particularly long explanation, it doesn't normally have to
be that verbose, but I probably won't ever complain about a changeset
text being too long rather than too short, independent of whether
it's a patch or a pull request.
Arnd
prev parent reply other threads:[~2012-11-16 17:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-05 11:09 [GIT PULL] arm-soc: Xilinx zynq changes for v3.8 Michal Simek
2012-11-06 15:52 ` Olof Johansson
2012-11-16 10:59 ` Michal Simek
2012-11-16 16:54 ` Arnd Bergmann
2012-11-16 17:13 ` Michal Simek
2012-11-16 17:46 ` Arnd Bergmann [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=201211161746.15629.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.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).