From: Benjamin Drung <benjamin.drung-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
To: Jason Gunthorpe <jgg-uk2M96/98Pc@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH rdma-core 3/3] debian: Update changelog to include Debian upload
Date: Tue, 14 Nov 2017 21:34:06 +0100 [thread overview]
Message-ID: <1510691646.4026.50.camel@profitbricks.com> (raw)
In-Reply-To: <20171114202823.GQ4263-uk2M96/98Pc@public.gmane.org>
Am Dienstag, den 14.11.2017, 13:28 -0700 schrieb Jason Gunthorpe:
> On Tue, Nov 14, 2017 at 12:33:30PM +0100, Benjamin Drung wrote:
> > rdma-core 15-1 was accepted in Debian. Include the changelog from
> > that
> > upload.
>
> I was thinking we'd keep the distro changelogs some place else? We
> are
> not going to try and store RH or suse changelogs for instance.
>
> Not a big deal for this one, obviously.
The advantage to include the changelog entries from Debian in the
master tree is that users can see that the packaging is the same and
that it is up-to-date. And user can see which version Debian package
version corresponds to the version from the master branch.
I can often find debian packaging from upstream projects that either
use their complete own packaging or a very outdated fork of the
packaging from Debian.
--
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
--
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:[~2017-11-14 20:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-14 11:33 [PATCH rdma-core 0/3] Debian packaging fixes Benjamin Drung
[not found] ` <20171114113330.2715-1-benjamin.drung-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
2017-11-14 11:33 ` [PATCH rdma-core 1/3] debian: Do not build ibacm for non-Linux architectures Benjamin Drung
2017-11-14 11:33 ` [PATCH rdma-core 2/3] debian: Do not require valgrind if not available Benjamin Drung
2017-11-14 11:33 ` [PATCH rdma-core 3/3] debian: Update changelog to include Debian upload Benjamin Drung
[not found] ` <20171114113330.2715-4-benjamin.drung-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
2017-11-14 20:28 ` Jason Gunthorpe
[not found] ` <20171114202823.GQ4263-uk2M96/98Pc@public.gmane.org>
2017-11-14 20:34 ` Benjamin Drung [this message]
[not found] ` <1510691646.4026.50.camel-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
2017-11-14 20:42 ` Jason Gunthorpe
[not found] ` <20171114204244.GU4263-uk2M96/98Pc@public.gmane.org>
2017-11-15 9:23 ` Benjamin Drung
[not found] ` <1510737831.4026.59.camel-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
2017-11-17 23:41 ` Jason Gunthorpe
2017-11-14 18:33 ` [PATCH rdma-core 0/3] Debian packaging fixes Leon Romanovsky
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=1510691646.4026.50.camel@profitbricks.com \
--to=benjamin.drung-eikl63zcoxah+58jc4qpia@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox