From: ori@eigenstate.org
To: 9fans@9fans.net
Subject: Re: [9fans] git/{diff,import}: make it easier to handle manually-asembled patch emails
Date: Sun, 22 Aug 2021 13:19:29 -0400 [thread overview]
Message-ID: <1A11CDED5E574B0DE2450041812175D2@eigenstate.org> (raw)
In-Reply-To: <534A6E599C225F5ED331BC1820BC4D13@eigenstate.org>
Quoth ori@eigenstate.org:
> Oops, sent to the wrong mailing list -- sorry about the noise.
>
Also, as a side note, it seems like the 9fans
mailing lists mangles patches -- if anyone
ever sends patches, they'll need to be sent
as attachments.
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T403f90e3b0509704-M61320344b346fd78f92b2b62
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
prev parent reply other threads:[~2021-08-22 17:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-22 17:10 ori
2021-08-22 17:12 ` ori
2021-08-22 17:19 ` ori [this message]
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=1A11CDED5E574B0DE2450041812175D2@eigenstate.org \
--to=ori@eigenstate.org \
--cc=9fans@9fans.net \
/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.
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 NNTP newsgroup(s).