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: Wed, 15 Nov 2017 10:23:51 +0100 [thread overview]
Message-ID: <1510737831.4026.59.camel@profitbricks.com> (raw)
In-Reply-To: <20171114204244.GU4263-uk2M96/98Pc@public.gmane.org>
Am Dienstag, den 14.11.2017, 13:42 -0700 schrieb Jason Gunthorpe:
> On Tue, Nov 14, 2017 at 09:34:06PM +0100, Benjamin Drung wrote:
>
> > 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.
>
> But it creates a technical problem, eg now that you are going to make
> a -2, where will the changelog commit go?
When all commits for -2 are accepted in the master branch, I would
update debian/changelog to have the 15-2 entry between 15-1 and 16-1.
An alternative would be to just have one changelog entry in the master
branch and document the basis, e.g.:
rdma-core (16-1) unstable; urgency=low
* New upstream release.
* Packaging is based on rdma-core 15-2 from Debian
* Downgrade debhelper to >= 9 to support Debian 7 & 8
-- Jason Gunthorpe <jgg-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org> Tue, 14 Nov 2017 12:24:09 +0100
> Ideally the changelog commit should match the actual git tree that
> was
> used to produce the debian source tar ball. Otherwise things start to
> get very confusing :)
>
> Jason
--
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-15 9:23 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
[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 [this message]
[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=1510737831.4026.59.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