From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: mate-desktop: update to 1.22.1.
Date: Thu, 06 Jun 2019 09:11:45 +0200 [thread overview]
Message-ID: <20190606071145.BVv9g_v1p86PDhDi6IWbWpXz2KSES61ynLjJZjDVBh8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-12157@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 454 bytes --]
New comment by Hoshpak on void-packages repository
https://github.com/void-linux/void-packages/pull/12157#issuecomment-499377140
Comment:
I don't mind having a lot of PRs. Having them separated makes it easier to review one by one and also allows travis to pass. However packages that depend on each other should better be in the same PR. I have seen at least one component that depends on mate-desktop and won't build without a current version of it.
next prev parent reply other threads:[~2019-06-06 7:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 0:15 [PR PATCH] " voidlinux-github
2019-06-05 1:45 ` voidlinux-github
2019-06-05 12:06 ` voidlinux-github
2019-06-05 12:31 ` voidlinux-github
2019-06-05 12:41 ` [PR PATCH] [Updated] " voidlinux-github
2019-06-05 12:41 ` voidlinux-github
2019-06-05 15:20 ` voidlinux-github
2019-06-06 6:28 ` voidlinux-github
2019-06-06 7:11 ` voidlinux-github [this message]
2019-06-06 7:12 ` [PR PATCH] [Merged]: " voidlinux-github
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=20190606071145.BVv9g_v1p86PDhDi6IWbWpXz2KSES61ynLjJZjDVBh8@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).