From: Jacob Hrbek <kreyren@rixotstudio.cz>
To: 53303@debbugs.gnu.org
Subject: [bug#53303] Acknowledgement ([PATCH] qBitTorrent: Bump version to avoid search engine fail)
Date: Sun, 16 Jan 2022 13:02:01 +0000 [thread overview]
Message-ID: <0cb5b6e1-4056-681d-4b6a-db6e329833fa@rixotstudio.cz> (raw)
In-Reply-To: <handler.53303.B.16423377689028.ack@debbugs.gnu.org>
[-- Attachment #1.1: Type: text/plain, Size: 884 bytes --]
DO NOT MERGE it fails again... seems to be on random investigating
On 1/16/22 13:57, help-debbugs@gnu.org wrote:
> Thank you for filing a new bug report with debbugs.gnu.org.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
> guix-patches@gnu.org
>
> If you wish to submit further information on this problem, please
> send it to 53303@debbugs.gnu.org.
>
> Please do not send mail to help-debbugs@gnu.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 53303: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=53303
> GNU Bug Tracking System
> Contact help-debbugs@gnu.org with problems
--
Jacob Hrbek
[-- Attachment #1.2: publickey - kreyren@rixotstudio.cz - 1677db82.asc --]
[-- Type: application/pgp-keys, Size: 713 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 249 bytes --]
next prev parent reply other threads:[~2022-01-16 13:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-16 12:55 [bug#53303] [PATCH] qBitTorrent: Bump version to avoid search engine fail Jacob Hrbek
[not found] ` <handler.53303.B.16423377689028.ack@debbugs.gnu.org>
2022-01-16 13:02 ` Jacob Hrbek [this message]
2022-01-19 6:24 ` bug#53303: (No Subject) Jacob Hrbek
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0cb5b6e1-4056-681d-4b6a-db6e329833fa@rixotstudio.cz \
--to=kreyren@rixotstudio.cz \
--cc=53303@debbugs.gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).