From: ori@eigenstate.org
To: 9front@9front.org
Subject: Re: [9front] Document -f option of `date` command (patch)
Date: Thu, 17 Jun 2021 17:24:40 -0400 [thread overview]
Message-ID: <72426DAC69CF87F597E84D06E690B0F1@eigenstate.org> (raw)
In-Reply-To: <baaf6e42-a942-c2f6-455a-7c22d9324a5a@itwont.work>
Quoth nihilazo <nico@itwont.work>:
> This is the first time I've ever submitted a patch to 9front so please
> tell me if I've got anything wrong! I couldn't find a style guide for
> manpages so I copied how existing ones were formatted the best I can.
Applied, thanks.
But -- for some reason your mail client mangled the
patch a bit; the lines that started with spaces had a
spare space perpended.
Not sure if there's a client setting you need to
change, or if you just need to attach next time.
next prev parent reply other threads:[~2021-06-18 5:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-17 18:02 nihilazo
2021-06-17 21:24 ` ori [this message]
2021-06-18 7:30 ` nihilazo
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=72426DAC69CF87F597E84D06E690B0F1@eigenstate.org \
--to=ori@eigenstate.org \
--cc=9front@9front.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.
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).