From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: Tmux update broke stuff // Ways how to handle breaking changes?
Date: Fri, 10 May 2019 08:16:21 +0200 [thread overview]
Message-ID: <20190510061621.agI20XYs4xD0_4BR5VjuGnSiso757AXIMdaksO6uwtM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-11606@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 467 bytes --]
New comment by the-maldridge on void-packages repository
https://github.com/void-linux/void-packages/issues/11606#issuecomment-491170078
Comment:
We have a way to handle breaking changes already. We strongly encourage our user base to take their problems to upstream so that upstream will stop making breaking changes without following appropriate steps.
If you're curious how certain things like SQL servers get upgraded, well the answer is meta-package magic.
prev parent reply other threads:[~2019-05-10 6:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-10 5:51 [ISSUE] " voidlinux-github
2019-05-10 6:16 ` [ISSUE] [CLOSED] " voidlinux-github
2019-05-10 6:16 ` voidlinux-github [this message]
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=20190510061621.agI20XYs4xD0_4BR5VjuGnSiso757AXIMdaksO6uwtM@z \
--to=voidlinux-github@inbox.vuxu.org \
--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).