From: Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
To: Or Gerlitz <ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Cc: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
linux-rdma <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: stalled again
Date: Wed, 2 Dec 2015 04:29:27 -0800 [thread overview]
Message-ID: <20151202122927.GC28278@infradead.org> (raw)
In-Reply-To: <565DCB24.7020304-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
On Tue, Dec 01, 2015 at 06:30:28PM +0200, Or Gerlitz wrote:
> Any reason on earth not to rebase your tree (== create new branch, move
> their the for-next tag) after an rc1 is out? how long does this take?
I'm not too worried about the base as there doesn't seem to be anything
pending for 4.5-rc right now. But the fact that nothing is pending
worries me a bit given that a lot of work is out there on the list and
even reviewed.
Maybe we need more co-maintainers if the two current maintainers can't
handle the workload?
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-12-02 12:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-01 16:30 stalled again Or Gerlitz
[not found] ` <565DCB24.7020304-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2015-12-01 17:33 ` Christoph Lameter
2015-12-01 18:13 ` Greg Kroah-Hartman
2015-12-02 12:29 ` Christoph Hellwig [this message]
[not found] ` <20151202122927.GC28278-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2015-12-02 18:42 ` Jason Gunthorpe
[not found] ` <20151202184201.GB17021-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2015-12-02 20:10 ` Doug Ledford
[not found] ` <565F5025.2090002-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-12-03 8:46 ` Christoph Hellwig
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=20151202122927.GC28278@infradead.org \
--to=hch-wegcikhe2lqwvfeawa7xhq@public.gmane.org \
--cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.