From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: vulkan-loader: update to 1.1.121
Date: Fri, 06 Sep 2019 08:01:27 +0200 [thread overview]
Message-ID: <20190906060127.liXRc9BFAhtmVndINOhUBiIQuIMeen_ohO5pNJ3RiA0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-14231@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 509 bytes --]
New comment by Hoshpak on void-packages repository
https://github.com/void-linux/void-packages/pull/14231#issuecomment-528721772
Comment:
Please don't split PRs like that. This way someone willing to merge basically has to manually pull your branch, rebase and compile locally to verify it works. There's nothing wrong with including several package updates in a PR if they depend on each other so travis can test both of them together. There just shouldn't be completely unrelated packages in the same PR.
next prev parent reply other threads:[~2019-09-06 6:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-06 4:30 [PR PATCH] " voidlinux-github
2019-09-06 6:01 ` voidlinux-github [this message]
2019-09-06 7:23 ` [PR PATCH] [Merged]: " voidlinux-github
2019-09-06 22:34 ` voidlinux-github
2019-09-07 17:45 ` 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=20190906060127.liXRc9BFAhtmVndINOhUBiIQuIMeen_ohO5pNJ3RiA0@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).