From: Or Gerlitz <ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
To: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: Greg Kroah-Hartman
<gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org>,
linux-rdma <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: stalled again
Date: Tue, 1 Dec 2015 18:30:28 +0200 [thread overview]
Message-ID: <565DCB24.7020304@mellanox.com> (raw)
Doug,
We're against into this... upstream is on 4.4-rc3 while your latest
branch in kernel.org (the one that carries thefor-next tag) is rebased
to 4.3-rc3...
--> our internal build and review systems for patches to linux-rdma
can'tmake any use of your tree. People here have to rebase their work
against their own clones of Linus tree and can't work with our internal
Gerrit rdma-next branch, etc, etc.
We have to work in a very inefficient manner.
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?
Or.
--
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 reply other threads:[~2015-12-01 16:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-01 16:30 Or Gerlitz [this message]
[not found] ` <565DCB24.7020304-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2015-12-01 17:33 ` stalled again Christoph Lameter
2015-12-01 18:13 ` Greg Kroah-Hartman
2015-12-02 12:29 ` Christoph Hellwig
[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=565DCB24.7020304@mellanox.com \
--to=ogerlitz-vpraknaxozvwk0htik3j/w@public.gmane.org \
--cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@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.