From: Andrew Morton <akpm@linux-foundation.org>
To: cbou@mail.ru
Cc: David Brownell <david-b@pacbell.net>, linux-kernel@vger.kernel.org
Subject: Re: gpiolib merge plans?
Date: Sat, 2 Feb 2008 11:12:14 -0800 [thread overview]
Message-ID: <20080202111214.8399b753.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080202112645.GA11453@zarina>
On Sat, 2 Feb 2008 14:26:45 +0300 Anton Vorontsov <cbou@mail.ru> wrote:
> Hello Andrew, David,
>
> I wonder what are the merge plans for gpiolib for 2.6.25? Are
> there any design issues that suppress merging?..
>
I'll merge it all.
>
> p.s. Sorry if I'm rubbing salt into the wound... but what
> happened to "-mm merge plans" emails?
I haven't got onto it, partly due to uncertainty about how bad 2.6.25 is
looking, partly because of how few 2.6.24-rcX-mmY releases there were,
partly because of how few people bothered testing those releases (case
study: did you? If not why not? Serious question.).
Sigh. I'll take a look at doing it this afternoon.
prev parent reply other threads:[~2008-02-02 19:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-02 11:26 gpiolib merge plans? Anton Vorontsov
2008-02-02 19:12 ` Andrew Morton [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=20080202111214.8399b753.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=cbou@mail.ru \
--cc=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.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).