From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Tegra updates for v3.1
Date: Fri, 15 Jul 2011 18:09:04 +0200 [thread overview]
Message-ID: <201107151809.04667.arnd@arndb.de> (raw)
In-Reply-To: <CAMbhsRQLaZss2uhLCaY-WjaH85WKLbYYnR2cfw4b+Qnz_rKXyw@mail.gmail.com>
On Friday 15 July 2011, Colin Cross wrote:
> If I put it in separate branches in the future, do you want a single
> pull request for a merge of the branches, or a pull request for each
> branch?
Separate requests. The idea is that I can group them together with
similar branches from other platforms and then send a single
pull request to Linus for e.g. all fixes, or a specific feature
getting added to multiple platforms.
The branches that I commonly have for other platforms are 'fixes',
'cleanup', 'devel' and 'board'. If you have a lot of patches, like
omap typically has, you can also do more specific feature branches.
In the future, I hope to see a lot more device tree work, which should
also have its own branch.
Arnd
prev parent reply other threads:[~2011-07-15 16:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-15 2:40 [GIT PULL] Tegra updates for v3.1 Colin Cross
2011-07-15 13:06 ` Arnd Bergmann
2011-07-15 14:00 ` Arnd Bergmann
2011-07-15 15:57 ` Colin Cross
2011-07-15 16:09 ` 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=201107151809.04667.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