From: Clemens Gruber <clemens.gruber@pqgruber.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] iperf: version bump
Date: Sat, 17 Dec 2016 20:51:10 +0100 [thread overview]
Message-ID: <20161217195110.GA18057@archie.localdomain> (raw)
In-Reply-To: <20161216151251.d7zdasxf5l43kh2v@pengutronix.de>
Hi,
On Fri, Dec 16, 2016 at 04:12:51PM +0100, Michael Olbrich wrote:
> Well, the configure options could use some cleanup in general, but that's
> nothing new.
You mean adding the (current) default options explicitly, right?
To sum up the update checklist:
1) Check the diff of the configure --help outputs between the versions
2) Check if options were missing/suboptimal before
3) Check if they are in alphabetical order
4) Check if there are new binaries/libraries
5) Move/remove the patches
6) Testing
Tooling would be nice. But probably not worth the effort. Maybe for the
download, extract and ./configure --help diff.. what do you think?
> And for all packages: I prefer it if the subject contains '<oldversion> ->
> <newversion>'. It makes review easier. That way it's easier to see which
> updates a small patch-level updates and require less review (and can be
> applied shortly before a release) and which require a deeper look.
I'll keep the subjects for the v2 but will use the -> notation next
time. (?)
Clemens
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2016-12-17 19:51 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-15 13:52 [ptxdist] [PATCH] collectd: update to 5.7.0 and add sensors support Clemens Gruber
2016-12-15 13:52 ` [ptxdist] [PATCH] dbus: bump version Clemens Gruber
2016-12-15 13:52 ` [ptxdist] [PATCH] file: " Clemens Gruber
2016-12-16 15:05 ` Michael Olbrich
2016-12-15 13:52 ` [ptxdist] [PATCH] glib: " Clemens Gruber
2016-12-15 13:52 ` [ptxdist] [PATCH] iperf: version bump Clemens Gruber
2016-12-16 15:12 ` Michael Olbrich
2016-12-17 19:51 ` Clemens Gruber [this message]
2017-01-04 16:33 ` Michael Olbrich
2017-01-04 20:34 ` Robert Schwebel
2016-12-15 13:52 ` [ptxdist] [PATCH] iproute2: bump version Clemens Gruber
2016-12-15 13:52 ` [ptxdist] [PATCH] projectroot: Fix HTML syntax in examples Clemens Gruber
2016-12-15 13:52 ` [ptxdist] [PATCH] rrdtool: update to 1.6.0 and make more modular Clemens Gruber
2016-12-16 15:22 ` Michael Olbrich
2016-12-15 13:52 ` [ptxdist] [PATCH] sqlite: bump version Clemens Gruber
2016-12-15 13:52 ` [ptxdist] [PATCH] systemd-bootchart: update to 231 Clemens Gruber
2016-12-15 13:52 ` [ptxdist] [PATCH] tmux: bump version Clemens Gruber
2016-12-16 15:25 ` Michael Olbrich
2016-12-15 13:52 ` [ptxdist] [PATCH] u-boot-tools: " Clemens Gruber
2016-12-15 13:52 ` [ptxdist] [PATCH] util-linux-ng: update to 2.29 and fix URL deduction Clemens Gruber
2016-12-16 15:30 ` Michael Olbrich
2016-12-15 13:52 ` [ptxdist] [PATCH] picocom: update to version 2.2 Clemens Gruber
2016-12-16 15:53 ` [ptxdist] [PATCH] collectd: update to 5.7.0 and add sensors support Michael Olbrich
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=20161217195110.GA18057@archie.localdomain \
--to=clemens.gruber@pqgruber.com \
--cc=ptxdist@pengutronix.de \
/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