All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Jason Gunthorpe <jgg-uk2M96/98Pc@public.gmane.org>
Subject: Re: Please update the linux-next location for the RDMA subsystem
Date: Wed, 29 Nov 2017 18:24:41 +0200	[thread overview]
Message-ID: <20171129162441.GC29104@mtr-leonro.local> (raw)
In-Reply-To: <9a80e43d-d32a-742b-fa6b-adacb152e8dd-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 2272 bytes --]

On Wed, Nov 29, 2017 at 11:12:44AM -0500, Doug Ledford wrote:
> On 11/19/17 1:46 AM, Leon Romanovsky wrote:
> > On Fri, Nov 17, 2017 at 02:47:40PM -0500, Doug Ledford wrote:
> >> Hi Stephen,
> >>
> >> Jason Gunthorpe is now co-maintaining the RDMA subsystem with me.  We
> >> have a shared repo that we can both write into.  I would like you to re-
> >> aim the RDMA linux-next pull point to:
> >>
> >> git://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma.git tags/for-
> >> next
> >
> > Doug,
> >
> > Does it make sense to get rid of "k.o" notation for for-next and for-rc branches?
> > It is already on kernel.org and seems to me as a redundant.
>
> Jason and I talked about this offline.  The reason it's there is
> actually more technical than anything else.  In order to have WIP
> branches that you want to quickly/easily get on github, but to not have
> them pollute k.o with WIP branches that haven't passed 0day yet, the
> easy solution is to add this to your .git/config for your kernel repo:
>
>         push = refs/heads/k.o/*:refs/heads/k.o/*
>         push = +refs/tags/for-linus*:refs/tags/for-linus*
>         push = +refs/tags/for-next*:refs/tags/for-next*
>         push = refs/heads/master:refs/heads/master
>
> That keeps only the stuff you really want going to k.o going there, and
> everything can then go to your WIP repository.  Going forward, whether
> Jason decides to use a github repo for 0day like I do or not, it now has
> a second benefit in that we can each have our own private namespace,
> which is basically anything not in k.o/, and treat the k.o/ namespace as
> a shared namespace where we worry about branch name conflicts, fast
> forward only updates, etc.  So, it's redundant to the people pulling,
> but I still think it has value for Jason and I.

AS long it works for both of you, we can live with that too.

My scheme is similar to you, but with one repo:
 * master - follow Linus's master
 * rdma-next/rdma-rc - submission queues equivalent to your k.o
 * topic/* - for on-going development
 * testing/* - different experiments

Thanks

>
> --
> Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
>     GPG KeyID: B826A3330E572FDD
>     Key fingerprint = AE6B 1BDA 122B 23B4 265B  1274 B826 A333 0E57 2FDD
>




[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      parent reply	other threads:[~2017-11-29 16:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-17 19:47 Please update the linux-next location for the RDMA subsystem Doug Ledford
     [not found] ` <1510948060.3973.29.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-11-19  3:56   ` Stephen Rothwell
     [not found]     ` <20171119145633.07a3a715-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2018-01-05 18:05       ` Jason Gunthorpe
     [not found]         ` <20180105180548.GD11972-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2018-01-06 15:01           ` Stephen Rothwell
     [not found]             ` <20180107020124.37a7eff1-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2018-01-10 20:53               ` Doug Ledford
     [not found]                 ` <1515617614.3403.163.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2018-01-11 20:16                   ` Stephen Rothwell
2017-11-19  6:46   ` Leon Romanovsky
     [not found]     ` <20171119064640.GV18825-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-11-29 16:12       ` Doug Ledford
     [not found]         ` <9a80e43d-d32a-742b-fa6b-adacb152e8dd-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-11-29 16:24           ` Leon Romanovsky [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=20171129162441.GC29104@mtr-leonro.local \
    --to=leon-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
    --cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=jgg-uk2M96/98Pc@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.