From: eric.y.miao@gmail.com (Eric Miao)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] pxa: patches for next merge window
Date: Tue, 2 Mar 2010 12:48:09 +0800 [thread overview]
Message-ID: <f17812d71003012048p2aabc731u141b6f9cf136cd34@mail.gmail.com> (raw)
In-Reply-To: <20100301151630.GA3002@n2100.arm.linux.org.uk>
On Mon, Mar 1, 2010 at 11:16 PM, Russell King - ARM Linux
<linux@arm.linux.org.uk> wrote:
> On Mon, Mar 01, 2010 at 09:23:37PM +0800, Eric Miao wrote:
>> Russell,
>>
>> Regarding the problem of my rebased three commits that were already
>> merged into your tree, I'm seeing three ways out:
>>
>> 1. merge back your devel branch (tried and as you suggested is not a
>> very clean way)
>>
>> 2. merge linus v2.6.33-rc? and get the other commits rebased
>>
>> 3. rebase all the other commits against your devel branch or (devel-stable)
>>
>> Just lemme know which is the best approach.
>>
>> BTW, it would be very helpful to us if we are able to understand the
>> difference and how you maintain 'devel' and 'devel-stable' branch?
>
> The devel branch is unstable - it's a combination of topic branches,
> and these topic branches are regularly re-merged to produce a single
> head for Stephen Rothwell to pull into -next. ?The other reason for
> publishing it is to give Nicolas (and others) something to look at so
> they know what's going on in my tree.
>
> It also occasionally receives truely unstable patches for testing
> purposes, which very well could be dropped - eg, if they cause build
> errors. ?(Remember - I have no practical way to test patches which
> affect many ARM platforms, except by getting linux-next to pick them
> up.)
>
> What this means is that the commit IDs of the merges and occasionally
> patches will change, and as such, basing anything on top of it is a
> recipe for disaster.
>
> In theory, the devel-stable branch receives merges of external trees,
> occasionally receives local merges from stable topic branches, but is
> never rebased and no commits are ever undone on it.
>
> So, basing patches on top of devel-stable should be safe.
>
> If you can arrange for your tree to be rebased upon devel-stable, that
> should solve the problem, and avoid any need to mess around with what's
> already committed there.
>
OK, rebased and pushed. Let me know if there are any remaining issues
during re-pull as I don't want block others from being pulled, feeling
guilty... ;-P
- eric
next prev parent reply other threads:[~2010-03-02 4:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-25 2:49 [GIT PULL] pxa: patches for next merge window Eric Miao
2010-02-25 20:51 ` Russell King - ARM Linux
2010-02-25 21:29 ` Russell King - ARM Linux
2010-02-26 2:50 ` Eric Miao
2010-02-26 9:05 ` Eric Miao
2010-02-28 16:14 ` Russell King - ARM Linux
2010-03-01 0:42 ` Nicolas Pitre
2010-03-01 13:23 ` Eric Miao
2010-03-01 15:16 ` Russell King - ARM Linux
2010-03-02 4:48 ` Eric Miao [this message]
2010-03-01 9:39 ` Uwe Kleine-König
2010-03-01 9:48 ` Russell King - ARM Linux
2010-03-01 10:11 ` Paul Mundt
2010-03-01 10:27 ` Uwe Kleine-König
2010-03-02 0:33 ` Stephen Rothwell
2010-03-01 10:12 ` Uwe Kleine-König
2010-03-01 16:40 ` Linus Torvalds
2010-03-01 16:58 ` Linus Torvalds
2010-03-01 17:07 ` Russell King - ARM Linux
-- strict thread matches above, loose matches on Subject: below --
2010-12-22 9:09 Eric Miao
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=f17812d71003012048p2aabc731u141b6f9cf136cd34@mail.gmail.com \
--to=eric.y.miao@gmail.com \
--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).