From: Vincent Legoll <vincent.legoll@gmail.com>
To: Felix Lechner <felix.lechner@lease-up.com>
Cc: 69331@debbugs.gnu.org, Arun Isaac <arunisaac@systemreboot.net>
Subject: bug#69331: Please provide links to Debbugs pages
Date: Fri, 21 Jun 2024 16:27:05 +0000 [thread overview]
Message-ID: <CAEwRq=prP3mM7v3U4NVbyCAMSb1pH0qn-wxqsEOEcYH+ZopSiQ@mail.gmail.com> (raw)
In-Reply-To: <87h6dmiana.fsf@lease-up.com>
Hello,
On Fri, Jun 21, 2024 at 3:22 PM Felix Lechner
<felix.lechner@lease-up.com> wrote:
> On Thu, Jun 20 2024, Vincent Legoll wrote:
> > the issues.guix.gnu.org web interface already shows all the info
>
> OKay, thanks for pointing that out! Where, please, may I see:
>
> 1. the email addresses of the conversants;
> 2. the package against which the report was filed;
> 3. the tags; and
> 4. the archive status.
I think there is some misunderstanding, I was not willing to say that
everything is shown by mumy.
I'm no native english speaker.
My error is probably: "already shows" => "would already show"
I wanted to say that even if eveything would be shown by mumy, the
link to debbugs would still be interesting to have. (this sentence I
have passed through an online translator, and it should properly
convey my thoughts, hopefuly).
> P.S. I'm looking at https://issues.guix.gnu.org/69381
I don't understand what you mean, with this other issue link.
--
Vincent Legoll
next prev parent reply other threads:[~2024-06-21 16:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 16:36 bug#69331: Please provide links to Debbugs pages Felix Lechner via Bug-mumi via Bug reports for GNU Guix Mumi.
2024-05-10 22:43 ` Arun Isaac
2024-06-20 18:40 ` Vincent Legoll
2024-06-21 15:22 ` Felix Lechner via Bug-mumi via Bug reports for GNU Guix Mumi.
2024-06-21 16:27 ` Vincent Legoll [this message]
2024-06-21 20:23 ` Felix Lechner via Bug-mumi via Bug reports for GNU Guix Mumi.
2024-06-24 23:08 ` Arun Isaac
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=prP3mM7v3U4NVbyCAMSb1pH0qn-wxqsEOEcYH+ZopSiQ@mail.gmail.com' \
--to=vincent.legoll@gmail.com \
--cc=69331@debbugs.gnu.org \
--cc=arunisaac@systemreboot.net \
--cc=felix.lechner@lease-up.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.