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: Mon, 1 Mar 2010 21:23:37 +0800 [thread overview]
Message-ID: <f17812d71003010523r6aa7cfd0va28b994dfadedeac@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1002281928200.10679@xanadu.home>
On Mon, Mar 1, 2010 at 8:42 AM, Nicolas Pitre <nico@fluxnic.net> wrote:
> On Sun, 28 Feb 2010, Russell King - ARM Linux wrote:
>
>> You've destroyed your original commits, so this calls into question my
>> entire 'devel-stable' branch.
>>
>> I've still not decided what to do about this. ?I'll ask Linus to merge
>> most of the 'devel' stuff without 'devel-stable' merged into mainline
>> to move stuff forward - this means _no_ _one's_ git work will be merged
>> through my tree, at least initially.
>>
>> However, I'm putting 'devel-stable' on hold; I'll let the other ARM git
>> maintainers discuss this and work out what they're going to do about
>> this mess. ?One solution is to destroy the 'devel-stable' branch in
>> its entirety, and get everyone to resend all their pull requests.
>> That's *not* nice.
>
> What about simply ignoring Eric's latest pull request and have your
> 'devel-stable' be merged by Linus as is? ?Surely the earlier branch you
> merged from Eric wasn't that bad anyway, and Eric can certainly provide
> new commits on top later on to fix possible issues with that in order to
> bring his stuff to the same state as what he just asked you to pull.
>
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?
- eric
next prev parent reply other threads:[~2010-03-01 13:23 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 [this message]
2010-03-01 15:16 ` Russell King - ARM Linux
2010-03-02 4:48 ` Eric Miao
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=f17812d71003010523r6aa7cfd0va28b994dfadedeac@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).