From: abenson <abenson@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: firebird3: update to 3.0.10
Date: Tue, 11 Jul 2023 02:29:47 +0200 [thread overview]
Message-ID: <20230711002947.7DJRXT5WmyeLoUDI4fBPAkrnMpDPKB5QjyuiIVpW3HA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44976@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 441 bytes --]
New comment by abenson on void-packages repository
https://github.com/void-linux/void-packages/pull/44976#issuecomment-1629917171
Comment:
Please don't open and close PRs as that makes it more difficult for us to track issues and needed changes.
In the future, please make the changes by [amending and squashing the existing](https://www.atlassian.com/git/tutorials/rewriting-history) commits and then force pushing to the same branch.
next prev parent reply other threads:[~2023-07-11 0:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-10 21:49 [PR PATCH] " onlylunix
2023-07-11 0:29 ` abenson [this message]
2023-07-11 13:45 ` [PR PATCH] [Updated] " onlylunix
2023-08-07 18:55 ` onlylunix
2023-08-26 8:00 ` firebird3: update to 3.0.11 sgn
2023-08-26 13:30 ` [PR PATCH] [Updated] " onlylunix
2023-08-26 13:32 ` onlylunix
2023-09-10 9:47 ` [PR PATCH] [Updated] " onlylunix
2023-09-10 12:59 ` onlylunix
2023-10-14 2:02 ` onlylunix
2023-10-14 2:09 ` [PR PATCH] [Updated] firebird3: update to 3.0.12.33717 onlylunix
2023-10-14 2:16 ` [PR PATCH] [Closed]: " onlylunix
2023-10-14 2:39 ` onlylunix
-- strict thread matches above, loose matches on Subject: below --
2023-03-15 17:05 [PR PATCH] firebird3: update to 3.0.10 onlylunix
2023-03-15 17:12 ` abenson
2023-03-17 13:11 ` onlylunix
2023-03-27 20:52 ` onlylunix
2023-03-27 22:53 ` abenson
2023-07-10 21:50 ` onlylunix
2023-03-14 3:10 [PR PATCH] " onlylunix
2023-03-15 11:40 ` abenson
2023-03-15 17:37 ` onlylunix
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=20230711002947.7DJRXT5WmyeLoUDI4fBPAkrnMpDPKB5QjyuiIVpW3HA@z \
--to=abenson@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).