From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: New Package: RabbitMQ C Client
Date: Mon, 28 Oct 2019 22:34:14 +0100 [thread overview]
Message-ID: <20191028213414.NPEOOOFoFAVTtEJOwZ5O2CbpHh1CUjWW3bQBMmG_ZBw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-15870@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 329 bytes --]
New comment by Johnnynator on void-packages repository
https://github.com/void-linux/void-packages/pull/15870#issuecomment-547156071
Comment:
> I will make another try.
You can normally just keep the PR open and just ammend your commit and force push to your repo. Keeps it all together and doesn't produce that much noise.
prev parent reply other threads:[~2019-10-28 21:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-28 20:30 [PR PATCH] " voidlinux-github
2019-10-28 21:29 ` voidlinux-github
2019-10-28 21:29 ` [PR PATCH] [Closed]: " voidlinux-github
2019-10-28 21:34 ` 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=20191028213414.NPEOOOFoFAVTtEJOwZ5O2CbpHh1CUjWW3bQBMmG_ZBw@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).