From: Richard Sent <richard@freakingpenguin.com>
To: Andreas Enge <andreas@enge.fr>
Cc: 73076@debbugs.gnu.org
Subject: bug#73076: Inputs for git:send-email
Date: Fri, 06 Sep 2024 12:26:57 -0400 [thread overview]
Message-ID: <874j6s7nou.fsf@freakingpenguin.com> (raw)
In-Reply-To: <ZtsqqOGtKymrKNbc@jurong> (Andreas Enge's message of "Fri, 6 Sep 2024 18:15:36 +0200")
I can confirm the same issue with git send-email.
--
Take it easy,
Richard Sent
Making my computer weirder one commit at a time.
next prev parent reply other threads:[~2024-09-06 16:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-06 16:15 bug#73076: Inputs for git:send-email Andreas Enge
2024-09-06 16:26 ` Richard Sent [this message]
2024-09-06 18:28 ` Ashish SHUKLA via Bug reports for GNU Guix
2024-09-09 12:10 ` bug#73030: " Simon Tournier
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=874j6s7nou.fsf@freakingpenguin.com \
--to=richard@freakingpenguin.com \
--cc=73076@debbugs.gnu.org \
--cc=andreas@enge.fr \
/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).