From: g.liakhovetski@gmx.de (Guennadi Liakhovetski)
To: linux-arm-kernel@lists.infradead.org
Subject: What's inside the pxa tree for this merge window
Date: Tue, 15 Sep 2009 09:55:45 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0909150950350.4640@axis700.grange> (raw)
In-Reply-To: <20090915073456.GA9208@n2100.arm.linux.org.uk>
On Tue, 15 Sep 2009, Russell King - ARM Linux wrote:
> On Tue, Sep 15, 2009 at 02:50:36PM +0800, Eric Miao wrote:
> > On Tue, Sep 15, 2009 at 2:30 PM, Guennadi Liakhovetski
> > <g.liakhovetski@gmx.de> wrote:
> > > On Mon, 14 Sep 2009, Russell King - ARM Linux wrote:
> > >
> > >> The request was for me to merge it into my tree. ?However, last Saturday
> > >> I asked Linus to pull my tree... still waiting, so I'm not going to merge
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > >> anything further until that's reached some resolution.
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > >>
> > >> It's a very bad idea to change trees after a pull request has been sent.
> > >
> > > Ic, Eric, when would you be pushing your tree then?
> > >
> >
> > Request has already been sent.
>
> It seems from your following email (to the pull request) that neither of
> you actually read what I said. The relevent bit is underlined with ^'s.
>
> It has now been merged, so I can now start merging stuff into my tree
> again.
I did read it, what I wasn't sure about is after
Eric has sent a pull request to you
you have sent a pull request to Linus
Linus has merged your tree
you can (and will) now pull further trees
whether you will be sending another pull request to Linus in this merge
window and if so - approximately when. Or whether because Eric's request
has missed your first pull request it now has to be pulled directly by
Linus to make it in this window. After this your reply it seems to be the
former, so, I'm hoping you'll be sending a next pull request to Linus with
PXA patches in your tree some time soon in this merge window.
Thanks
Guennadi
---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer
http://www.open-technology.de/
next prev parent reply other threads:[~2009-09-15 7:55 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-10 11:46 What's inside the pxa tree for this merge window Eric Miao
2009-09-10 11:54 ` Daniel Mack
2009-09-10 12:15 ` Guennadi Liakhovetski
2009-09-10 12:23 ` Eric Miao
2009-09-10 12:32 ` Daniel Mack
2009-09-10 12:35 ` Eric Miao
2009-09-10 12:44 ` Daniel Mack
2009-09-10 13:05 ` Guennadi Liakhovetski
2009-09-10 13:09 ` Daniel Mack
2009-09-14 11:03 ` Guennadi Liakhovetski
2009-09-14 11:11 ` Russell King - ARM Linux
2009-09-15 6:30 ` Guennadi Liakhovetski
2009-09-15 6:50 ` Eric Miao
2009-09-15 7:34 ` Russell King - ARM Linux
2009-09-15 7:55 ` Guennadi Liakhovetski [this message]
2009-09-18 6:43 ` Matej Kenda
2009-09-18 6:47 ` Eric Miao
2009-09-18 7:45 ` Russell King - ARM Linux
2009-09-21 19:19 ` Guennadi Liakhovetski
2009-09-21 20:09 ` Russell King - ARM Linux
2009-09-21 20:32 ` Jamie Lokier
2009-09-30 12:09 ` arm tree in broken state (was Re: What's inside the pxa tree for this merge window) Pavel Machek
2009-09-30 12:16 ` Guennadi Liakhovetski
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=Pine.LNX.4.64.0909150950350.4640@axis700.grange \
--to=g.liakhovetski@gmx.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