From: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: "Saleem,
Shiraz" <shiraz.saleem-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
"linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [ANNOUNCE] Shared pull requests (was Re: Workflow for i40iw patch submissions)
Date: Tue, 26 Sep 2017 19:21:40 +0300 [thread overview]
Message-ID: <20170926162140.GF6816@mtr-leonro.local> (raw)
In-Reply-To: <6fa41141-cae5-da51-94ef-afe5bdec22bd-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 837 bytes --]
On Tue, Sep 26, 2017 at 12:03:01PM -0400, Doug Ledford wrote:
<...>
> >> He started to complain about empty merge commit with v4.13-rc1, and continued with explanations
> >> about difference between back and forward merges. From my point of view, my intention to base
> >> shared pull request on latest -rcX is exactly forward (good) merge, because it ensures that
> >> all our future submissions for net/net-next/rdma-rc/rdma-next are completely in sync and
> >> ready to go.
>
> This is why, when I submit a pull request for -rc, I also merge it into
> for-next. It keeps this up to date as you say, without needing to pull
> in all of the -rc, so it gives Linus an easier history to look at. It
> does not, however, sync up the net side of things.
>
Doug,
What is the bottom line for the bases for shared pull requests?
Thanks
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-09-26 16:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9DD61F30A802C4429A01CA4200E302A75B9FB085@fmsmsx116.amr.corp.intel.com>
[not found] ` <9DD61F30A802C4429A01CA4200E302A75B9FB085-5FK+k9557ZBZtRGVdHMbwrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2017-09-23 15:03 ` [ANNOUNCE] Shared pull requests (was Re: Workflow for i40iw patch submissions) Doug Ledford
[not found] ` <1506179005.120853.67.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-09-24 19:56 ` Jason Gunthorpe
[not found] ` <20170924195627.GB18007-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-09-25 4:23 ` Leon Romanovsky
[not found] ` <20170925042355.GM25094-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-09-26 3:33 ` Jason Gunthorpe
[not found] ` <20170926033343.GA10193-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-09-26 5:28 ` Leon Romanovsky
[not found] ` <20170926052805.GC1230-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-09-28 15:53 ` Jason Gunthorpe
2017-09-25 6:42 ` Christoph Hellwig
2017-09-25 3:59 ` Leon Romanovsky
[not found] ` <20170925035910.GL25094-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-09-25 14:53 ` Doug Ledford
[not found] ` <5abacb7d-3e86-4e12-ce95-a8fe472a6a09-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-09-25 15:57 ` Leon Romanovsky
[not found] ` <20170925155749.GO25094-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-09-26 2:31 ` Doug Ledford
[not found] ` <7c01cef3-0471-8339-3498-1d9ec4f8a9d3-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-09-26 5:13 ` Leon Romanovsky
[not found] ` <20170926051349.GA1230-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-09-26 6:56 ` Leon Romanovsky
[not found] ` <20170926065600.GA6816-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-09-26 16:03 ` Doug Ledford
[not found] ` <6fa41141-cae5-da51-94ef-afe5bdec22bd-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-09-26 16:20 ` Doug Ledford
2017-09-26 16:21 ` Leon Romanovsky [this message]
[not found] ` <20170926162140.GF6816-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-09-26 16:23 ` Doug Ledford
[not found] ` <4707c600-7aec-2c14-11d6-0443c2a835e3-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-09-26 16:34 ` Leon Romanovsky
2017-09-28 16:29 ` Jason Gunthorpe
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=20170926162140.GF6816@mtr-leonro.local \
--to=leon-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=shiraz.saleem-ral2JQCrhuEAvxtiuMwx3w@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox