From: "Clément Lassieur" <clement@lassieur.org>
To: "Wilko Meyer" <w@wmeyer.eu>
Cc: 68738@debbugs.gnu.org
Subject: [bug#68738] (no subject)
Date: Sun, 28 Jan 2024 00:36:27 +0000 [thread overview]
Message-ID: <caa43216-305e-4b1c-ab9a-7c46615d56c7@app.fastmail.com> (raw)
In-Reply-To: <871qa2s66p.fsf@wmeyer.eu>
[-- Attachment #1: Type: text/plain, Size: 987 bytes --]
Well don't worry this happened to all of us ;)
Welcome
On Sat, Jan 27, 2024, at 11:24 PM, Wilko Meyer wrote:
>
> Hi Clément,
>
> Clément Lassieur <clement@lassieur.org> writes:
>
> > If you don't want to send an email to human people, you can just mail
> > control@debbugs.gnu.org, with no subject, and with content: "close
> > xxxxx". (It won't get into people's inbox.)
> >
> > Explanations here: https://debbugs.gnu.org/server-control.html.
>
> Thanks for the tip & for taking the time to explain this to me! This
> would've been the better option (accidentally send a patch-series to
> guix-patches@debbugs.gnu.org instead of to the specific issue created by
> the cover letter, so I had to clean up wrongfully created issues) in
> this case and would've caused less clutter. I'll take some time to read
> up on the debbugs documentation as I'm not too familiar with it as a
> tool yet!
>
> --
> Kind regards,
>
> Wilko Meyer
> w@wmeyer.eu
>
[-- Attachment #2: Type: text/html, Size: 1792 bytes --]
next prev parent reply other threads:[~2024-01-28 0:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-26 15:12 [bug#68740] [PATCH 1/7] gnu: linux-libre 6.7: Update to 6.7.2 Wilko Meyer
2024-01-26 15:12 ` [bug#68737] [PATCH 2/7] gnu: linux-libre 6.6: Update to 6.6.14 Wilko Meyer
2024-01-26 15:27 ` bug#68737: (no subject) Wilko Meyer
2024-01-26 15:30 ` [bug#68737] " Wilko Meyer
2024-01-26 15:12 ` [bug#68739] [PATCH 3/7] gnu: linux-libre 6.1: Update to 6.1.75 Wilko Meyer
2024-01-26 15:31 ` bug#68739: (no subject) Wilko Meyer
2024-01-26 15:12 ` [bug#68740] [PATCH 4/7] gnu: linux-libre 5.15: Update to 5.15.148 Wilko Meyer
2024-01-26 15:12 ` [bug#68738] [PATCH 5/7] gnu: linux-libre 5.10: Update to 5.10.209 Wilko Meyer
2024-01-26 15:34 ` bug#68738: (no subject) Wilko Meyer
2024-01-26 22:21 ` [bug#68738] " Clément Lassieur
2024-01-27 23:24 ` Wilko Meyer
2024-01-28 0:36 ` Clément Lassieur [this message]
2024-01-26 15:12 ` [bug#68740] [PATCH 6/7] gnu: linux-libre 5.4: Update to 5.4.268 Wilko Meyer
2024-01-26 15:12 ` [bug#68740] [PATCH 7/7] gnu: linux-libre 4.19: Update to 4.19.306 Wilko Meyer
2024-01-26 15:29 ` bug#68740: (no subject) Wilko Meyer
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=caa43216-305e-4b1c-ab9a-7c46615d56c7@app.fastmail.com \
--to=clement@lassieur.org \
--cc=68738@debbugs.gnu.org \
--cc=w@wmeyer.eu \
/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).