From: Luther Thompson <lutheroto@gmail.com>
To: Ben Sturmfels <ben@sturm.com.au>
Cc: 35303@debbugs.gnu.org
Subject: bug#35303:
Date: Thu, 25 Apr 2019 01:57:35 -0400 [thread overview]
Message-ID: <08fa8bc55e007b62fff50c0a02c25fa39f8d681a.camel@gmail.com> (raw)
In-Reply-To: <874l6omcoa.fsf@sturm.com.au>
On Wed, 2019-04-24 at 11:09 +1000, Ben Sturmfels wrote:
> On Wed, 17 Apr 2019, Luther Thompson wrote:
>
> > unsubscribe
>
> Hi Luther,
>
> You'll probably want to unsubscribe from the mailing list here:
> https://lists.gnu.org/mailman/options/bug-guix
Thanks, but I've already taken care of it. It's just hard to get the "-
request" address right, sometimes.
Luther
next prev parent reply other threads:[~2019-04-25 5:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <a828fcfde16058b88de22195b15148e7b375e4cc.camel@gmail.com>
2019-04-24 1:09 ` bug#35303: Ben Sturmfels
2019-04-25 5:57 ` Luther Thompson [this message]
2019-04-25 7:37 ` bug#35303: Ricardo Wurmus
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=08fa8bc55e007b62fff50c0a02c25fa39f8d681a.camel@gmail.com \
--to=lutheroto@gmail.com \
--cc=35303@debbugs.gnu.org \
--cc=ben@sturm.com.au \
/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).