linux-rdma.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Drung <benjamin.drung-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
To: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: Linux RDMA Mailing List
	<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: rdma-core debian/master branch
Date: Tue, 14 Nov 2017 20:01:06 +0100	[thread overview]
Message-ID: <1510686066.4026.43.camel@profitbricks.com> (raw)
In-Reply-To: <20171114184725.GH18825-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>

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

Am Dienstag, den 14.11.2017, 20:47 +0200 schrieb Leon Romanovsky:
> On Tue, Nov 14, 2017 at 12:21:10PM +0100, Benjamin Drung wrote:
> > Hi,
> > 
> > I have a debian/master branch in my personal rdma-core fork:
> > https://github.com/bdrung/rdma-core/commits/debian/master
> > In addition, I tagged the upload with debian/15-1.
> > 
> > This branch contains the exact content of the uploaded package to
> > Debian. It would be nice if this branch could be included in the
> > linux-
> > rdma/rdma-core repository.
> 
> Is it possible to align it with stable-v15 branch?

Not really. This branch is more or less aligned with the master branch
(as long as Debian does not hit the feature freeze), i.e. I will upload
rdma-core 16 to Debian unstable once it is released (instead of 15.1).

And I will do an 15-2 upload to address the build failures. So there is
some divergence (at least in debian/changelog).

-- 
Benjamin Drung
System Developer
Debian & Ubuntu Developer

ProfitBricks GmbH
Greifswalder Str. 207
D - 10405 Berlin

Email: benjamin.drung-EIkl63zCoXaH+58JC4qpiA@public.gmane.org
URL: https://www.profitbricks.de

Sitz der Gesellschaft: Berlin
Registergericht: Amtsgericht Charlottenburg, HRB 125506 B
Geschäftsführer: Achim Weiss, Matthias Steinberg

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

  parent reply	other threads:[~2017-11-14 19:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-14 11:21 rdma-core debian/master branch Benjamin Drung
     [not found] ` <1510658470.4026.27.camel-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
2017-11-14 18:47   ` Leon Romanovsky
     [not found]     ` <20171114184725.GH18825-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-11-14 19:01       ` Benjamin Drung [this message]
     [not found]         ` <1510686066.4026.43.camel-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
2017-11-16  6:47           ` Leon Romanovsky
     [not found]             ` <20171116064730.GG18825-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-11-16  8:58               ` Benjamin Drung
     [not found]                 ` <1510822703.4026.79.camel-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
2017-11-16  9:17                   ` Leon Romanovsky
2017-11-17  0:12                   ` Jason Gunthorpe
2017-11-18  7:32   ` Leon Romanovsky
     [not found]     ` <20171118073252.GR18825-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-11-30 11:24       ` Benjamin Drung

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=1510686066.4026.43.camel@profitbricks.com \
    --to=benjamin.drung-eikl63zcoxah+58jc4qpia@public.gmane.org \
    --cc=leon-DgEjT+Ai2ygdnm+yROfE0A@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 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).