From: Ian Eure <ian@retrospec.tv>
To: guix-devel <guix-devel@gnu.org>
Subject: Did something with format-patch or send-email break?
Date: Sat, 08 Jun 2024 17:22:30 -0700 [thread overview]
Message-ID: <87jzizt01a.fsf@meson> (raw)
I’m not sure of the precise mechanism employed, but I believe that
that in the past, if I ran `git format-patch' and `git
send-email', it would send an email to the right place. This is
implied by the manual, which doesn’t mention a patch submission
email address, except for an issue number address when sending a
patch series.
This doesn’t seem to work anymore; the output of `git
format-patch' has no To: header populated, so `git send-email'
asks me where:
meson!ieure:~/Projects/guix/staging$ guix describe
Generation 13 Jun 08 2024 17:39:39 (current)
atomized 6bb138d
repository URL:
https://codeberg.org/ieure/atomized-guix.git
branch: main
commit: 6bb138db5b7f56f399c9cb2e0b45fecaa8cd0182
guix bc8a41f
repository URL: https://git.savannah.gnu.org/git/guix.git
branch: master
commit: bc8a41f4a8d9f1f0525d7bc97c67ed3c8aea3111
meson!ieure:~/Projects/guix/staging$ git log --oneline
HEAD^..HEAD
bc8a41f4a8 (HEAD -> master, upstream/master) gnu: mes: Update
to 0.26.1.
meson!ieure:~/Projects/guix/staging$ echo "changes" >>
gnu/packages/python-xyz.scm && git ci -am "changes"
[master 88e3f97240] changes
1 file changed, 2 insertions(+)
meson!ieure:~/Projects/guix/staging$ git format-patch -1
0001-changes.patch
meson!ieure:~/Projects/guix/staging$ git send-email
0001-changes.patch
0001-changes.patch
To whom should the emails be sent (if anyone)? C-c C-c
meson!ieure:~/Projects/guix/staging$
Reproduced on Guix System, Guix on Debian (which the above output
is from), and someone in #guix also reproduced it.
Is it broken? Am I missing one of the numerous intricate fiddly
bits of setup to make email patch flow work? The manual’s "The
Perfect Setup" section only mentions Geiser and yasnippet setup,
which isn’t relevant to this.
Thanks,
— Ian
next reply other threads:[~2024-06-09 0:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-09 0:22 Ian Eure [this message]
2024-06-09 10:19 ` Did something with format-patch or send-email break? Tomas Volf
2024-06-09 10:51 ` Tomas Volf
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=87jzizt01a.fsf@meson \
--to=ian@retrospec.tv \
--cc=guix-devel@gnu.org \
/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).