all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Vincent Legoll <vincent.legoll@gmail.com>
To: John Kehayias <john.kehayias@protonmail.com>
Cc: Greg Hogan <code@greghogan.com>,
	Maxim Cournoyer <maxim.cournoyer@gmail.com>,
	66703@debbugs.gnu.org
Subject: bug#66703: Broken link to Debbugs User Guide
Date: Mon, 9 Dec 2024 18:44:18 +0000	[thread overview]
Message-ID: <CAEwRq=pmGs46fU4qPx5f7pPkcNZiY1bC+U7w6S7pz8iMi5vsYg@mail.gmail.com> (raw)
In-Reply-To: <87cyi1r4dh.fsf@protonmail.com>

[-- Attachment #1: Type: text/plain, Size: 700 bytes --]

Hello,

On Mon, Dec 9, 2024 at 2:12 AM John Kehayias <john.kehayias@protonmail.com>
wrote:

> (There was a patch from Vincent Legoll that was lost as it was only sent
> to the bug number, which goes nowhere:
>

Yes, I did not use the tool (mumi CLI ?) to reply, so I just sent to the
bug number
hoping it would reach the interested people. I think an easy CC list that
you can
copy/paste would be a nice UI feature for mumi web.


> <https://issues.guix.gnu.org/66703#5> This just removes the reference
> though. Adding to the CC here.)
>

Yep, not knowing what was wanted/useful I just went for the simple Occam
fix.

Thanks for reviving the issue !

-- 
Vincent Legoll

[-- Attachment #2: Type: text/html, Size: 1463 bytes --]

  reply	other threads:[~2024-12-09 18:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-23 14:51 bug#66703: Broken link to Debbugs User Guide Greg Hogan
2023-10-24  2:39 ` Maxim Cournoyer
2023-10-27  2:42 ` John Kehayias via Bug reports for GNU Guix
2023-10-31 15:19   ` Maxim Cournoyer
2024-12-09  2:12     ` John Kehayias via Bug reports for GNU Guix
2024-12-09 18:44       ` Vincent Legoll [this message]
2024-06-15 12:01 ` bug#66703: [PATCH] doc: Remove 'Debbugs User Guide' broken links Vincent Legoll

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='CAEwRq=pmGs46fU4qPx5f7pPkcNZiY1bC+U7w6S7pz8iMi5vsYg@mail.gmail.com' \
    --to=vincent.legoll@gmail.com \
    --cc=66703@debbugs.gnu.org \
    --cc=code@greghogan.com \
    --cc=john.kehayias@protonmail.com \
    --cc=maxim.cournoyer@gmail.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.