all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: jbranso--- via Bug reports for GNU Guix <bug-guix@gnu.org>
To: "Antonio Carlos Padoan Junior" <acpadoanjr@yahoo.com.br>
Cc: olivier.dion@polymtl.ca, 70850@debbugs.gnu.org
Subject: bug#70850: question on nss-certs
Date: Fri, 10 May 2024 14:21:05 +0000	[thread overview]
Message-ID: <a1395dffa644091fb8f18b6d79f9bddbced7d3f5@dismail.de> (raw)
In-Reply-To: <871q6a1af5.fsf@yahoo.com.br>

May 10, 2024 at 1:51 AM, "Antonio Carlos Padoan Junior" <acpadoanjr@yahoo.com.br> wrote:



> 
> jbranso@dismail.de writes:
> 
> > 
> > May 9, 2024 at 1:53 PM, "Olivier Dion" <olivier.dion@polymtl.ca> wrote:
> > 
> >  The best place for bugs, is to discuss them on bug-guix@gnu.org. That way 
> > 
> >  it ends up in our bug tracker. guix-devel@gnu.org is really meant for
> > 
> >  massive cool changes that you want guix to include. :)
> > 
> 
> Thank you, I was not certain it was a bug. And yes, next time I will try
> 
> to be more precise in which list to post.

No worries.  I hope the bug gets fixed.  :)

> 
> -- 
> 
> Antonio Carlos PADOAN JUNIOR
> 
> PGP fingerprint:
> 
> 243F 237F 2DD3 4DCA 4EA3 1341 2481 90F9 B421 A6C9
>




  reply	other threads:[~2024-05-10 14:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87o79fkkam.fsf.ref@yahoo.com.br>
2024-05-09 16:43 ` question on nss-certs Antonio Carlos Padoan Junior
2024-05-09 17:53   ` Olivier Dion
2024-05-09 22:13     ` bug#70850: " jbranso--- via Bug reports for GNU Guix
2024-05-10  5:51       ` Antonio Carlos Padoan Junior via Bug reports for GNU Guix
2024-05-10 14:21         ` jbranso--- via Bug reports for GNU Guix [this message]
2024-05-16  2:58           ` Maxim Cournoyer

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=a1395dffa644091fb8f18b6d79f9bddbced7d3f5@dismail.de \
    --to=bug-guix@gnu.org \
    --cc=70850@debbugs.gnu.org \
    --cc=acpadoanjr@yahoo.com.br \
    --cc=jbranso@dismail.de \
    --cc=olivier.dion@polymtl.ca \
    /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.