From: Tony Lindgren <tony@atomide.com>
To: "Woodruff, Richard" <r-woodruff2@ti.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: FW: Fwd: Re: [PATCH 0/14] more assorted stuff for 2.6.26-rc1
Date: Mon, 28 Apr 2008 15:10:11 -0700 [thread overview]
Message-ID: <20080428221009.GB8449@atomide.com> (raw)
In-Reply-To: <3B6D69C3A9EBCA4BA5DA60D913027429042C59DB@dlee13.ent.ti.com>
* Woodruff, Richard <r-woodruff2@ti.com> [080428 15:02]:
> Tony,
>
> Would you participate in this?
Sure, that will help to see any upcoming conflicts for omap-upstream
branches.
Tony
> Regards,
> Richard W.
>
>
>
> > -----Original Message-----
> > From: linux-arm-kernel-bounces@lists.arm.linux.org.uk
> > [mailto:linux-arm-kernel-bounces@lists.arm.linux.org.uk] On
> > Behalf Of Nicolas Pitre
> > Sent: Monday, April 28, 2008 4:29 PM
> > To: Andrew Morton
> > Cc: Russell King - ARM Linux; linux-arm-kernel@lists.arm.linux.org.uk
> > Subject: Re: Fwd: Re: [PATCH 0/14] more assorted stuff for 2.6.26-rc1
> >
> > On Mon, 28 Apr 2008, Andrew Morton wrote:
> >
> > > They are, of course, what I refer to as private trees. For
> > want of a
> > > better term. I believe that probably your misundertanding was
> > > deliberate and certainly your obtusensss is deliberate.
> > >
> > > No progress is being made here.
> >
> > OK. Progress you want? Let's go for it.
> >
> > Unless someone else steps forward for the job, I'm going to
> > gather every one else's ARM related git tree into one, and
> > push for that combined repository to be merged into
> > linux-next. I'll include my stuff (obviously), RMK's stuff
> > (git will cope if the same changes come from different
> > paths), Catalin's stuff, and anyone with a Git tree who sends
> > me a request. That is also good for those i.mx folks who are
> > complaining about the lack of attention for their patches, etc. etc.
> >
> > The requirements are:
> >
> > - it must be a git repository accessible through the git:// protocol;
> >
> > - the tree must build;
> >
> > - it must merge easily with what I already have;
> >
> > - it will be excluded with notification if it causes
> > problems upstream
> > until those problems are resolved and a new request is sent to me;
> >
> > - I may change those requirements as I see fit.
> >
> > What about this? What do people think?
> >
> >
> > Nicolas
> >
> > -------------------------------------------------------------------
> > List admin:
> > http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm-kernel
> > FAQ: http://www.arm.linux.org.uk/mailinglists/faq.php
> > Etiquette: http://www.arm.linux.org.uk/mailinglists/etiquette.php
> >
prev parent reply other threads:[~2008-04-28 22:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-28 22:02 FW: Fwd: Re: [PATCH 0/14] more assorted stuff for 2.6.26-rc1 Woodruff, Richard
2008-04-28 22:10 ` Tony Lindgren [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=20080428221009.GB8449@atomide.com \
--to=tony@atomide.com \
--cc=linux-omap@vger.kernel.org \
--cc=r-woodruff2@ti.com \
/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