From: kruceter <kruceter@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: telegram-desktop: update to 4.6.1.
Date: Tue, 07 Feb 2023 07:58:10 +0100 [thread overview]
Message-ID: <20230207065810.8RU2ZFeYiVWwLAuMckjKiS6u9rG8ax8_uzAR9x8yFFM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42126@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 371 bytes --]
New comment by kruceter on void-packages repository
https://github.com/void-linux/void-packages/pull/42126#issuecomment-1420284808
Comment:
A piece of advice for your future pull requests: please do not close them just because version has changed during that time.
Just change the version, fix the commit message, `git push -f` and change title of the pull request.
next prev parent reply other threads:[~2023-02-07 6:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-07 6:38 [PR PATCH] " baalajimaestro
2023-02-07 6:57 ` kruceter
2023-02-07 6:57 ` kruceter
2023-02-07 6:58 ` kruceter [this message]
2023-02-07 11:33 ` [PR PATCH] [Merged]: " Johnnynator
2023-02-08 2:23 ` baalajimaestro
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=20230207065810.8RU2ZFeYiVWwLAuMckjKiS6u9rG8ax8_uzAR9x8yFFM@z \
--to=kruceter@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).