From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] DaVinci cleanups for v3.4
Date: Tue, 28 Feb 2012 15:27:39 +0000 [thread overview]
Message-ID: <201202281527.39302.arnd@arndb.de> (raw)
In-Reply-To: <DF0F476B391FA8409C78302C7BA518B6317D6BF8@DBDE01.ent.ti.com>
On Tuesday 28 February 2012, Nori, Sekhar wrote:
> I guess the cleanest way to do that would have been to let
> these patches go through my tree with appropriate maintainer
> acks (but that obviously didn't happen - will try and fix
> that for future). Per my understanding, it is encouraged that
> a patch should get applied only through one tree, so I was
> reluctant to apply them to any of the branches I send to you
> after they were already in linux-next through other trees.
That is correct, we generally try to avoid duplicating commits
but instead use branches that are based on a common history
containing whatever is needed in multiple places.
Note that the patch I applied does not duplicate the ones that
went into the other trees, it recreates dummy header files
instead and needs to be reverted at some point in the future
when everything has been merged.
Arnd
next prev parent reply other threads:[~2012-02-28 15:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-24 21:25 [GIT PULL] DaVinci cleanups for v3.4 Nori, Sekhar
2012-02-27 14:59 ` Arnd Bergmann
2012-02-28 14:23 ` Nori, Sekhar
2012-02-28 15:27 ` Arnd Bergmann [this message]
2012-02-28 16:50 ` Nori, Sekhar
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=201202281527.39302.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.