From: Jlll1 <Jlll1@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: CopyQ: Update to 6.0.1
Date: Mon, 03 Jan 2022 08:30:12 +0100 [thread overview]
Message-ID: <20220103073012.uZtfE0eK6bRPCZ5HnNn9YtBfQnMrb0HO3y3H6IaqiSg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34812@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 266 bytes --]
New comment by Jlll1 on void-packages repository
https://github.com/void-linux/void-packages/pull/34812#issuecomment-1003912082
Comment:
I messed up and deleted this branch and now I can't seem to be able to recover it to fix this lint issue, so I'm closing this.
next prev parent reply other threads:[~2022-01-03 7:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-02 19:44 [PR PATCH] " Jlll1
2022-01-03 7:30 ` Jlll1 [this message]
2022-01-03 7:30 ` [PR PATCH] [Closed]: " Jlll1
2022-01-04 1:58 [PR PATCH] CopyQ: update " ram02z
2022-01-05 7:25 ` ericonr
2022-01-05 15:03 ` mobinmob
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=20220103073012.uZtfE0eK6bRPCZ5HnNn9YtBfQnMrb0HO3y3H6IaqiSg@z \
--to=jlll1@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).