From: q66 <q66@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] R: update to 4.0.3.
Date: Fri, 16 Oct 2020 16:51:16 +0200 [thread overview]
Message-ID: <20201016145116.rTt9gpMKEnw4pyVDepuudDnlnSIDmkGbWjyc6nasyx4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25653@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 492 bytes --]
New review comment by q66 on void-packages repository
https://github.com/void-linux/void-packages/pull/25653#discussion_r506506349
Comment:
updating shlibs without revbumping is actually fine but it depends on circumstances
usually you'd bump the version in shlibs if the new version introduced some API that packages are going to use (as in that case, the packages built against the newer version will require it, while packages built against the older one will keep working just fine)
next prev parent reply other threads:[~2020-10-16 14:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-16 11:31 [PR PATCH] " luhann
2020-10-16 14:34 ` [PR REVIEW] " ahesford
2020-10-16 14:51 ` q66 [this message]
2020-10-16 14:51 ` q66
2020-10-16 21:47 ` luhann
2020-10-16 21:51 ` [PR PATCH] [Updated] " luhann
2020-10-17 15:57 ` [PR PATCH] [Merged]: " ahesford
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=20201016145116.rTt9gpMKEnw4pyVDepuudDnlnSIDmkGbWjyc6nasyx4@z \
--to=q66@users.noreply.github.com \
--cc=ml@inbox.vuxu.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).