From: Eric Wong <e@80x24.org>
To: James Rowe <jnrowe@gmail.com>
Cc: dtas-all@nongnu.org
Subject: Re: [PATCH] doc: trivial typo fixes
Date: Sat, 9 Nov 2019 09:17:48 +0000 [thread overview]
Message-ID: <20191109091748.GA24003@dcvr> (raw)
In-Reply-To: <20191104093530.21775-1-jnrowe@gmail.com>
James Rowe <jnrowe@gmail.com> wrote:
> I’m entirely unaware of how to use git-send-email, so hopefully this
> email arrives and is formatted correctly. Feel free to reply with abuse
> if it isn’t ;)
Thanks, everything seems fine. Applied and pushed.
Btw, I've been working throughout the years on to ensure
software development isn't tied to a single provider. So
hopefully git-send-email (and other tools around email) aren't
too tough to learn. I (and other git hackers) @
git@vger.kernel.org can probably improve it, further.
prev parent reply other threads:[~2019-11-09 9:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-04 9:35 [PATCH] doc: trivial typo fixes James Rowe
2019-11-09 9:17 ` Eric Wong [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
List information: https://80x24.org/dtas/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191109091748.GA24003@dcvr \
--to=e@80x24.org \
--cc=dtas-all@nongnu.org \
--cc=jnrowe@gmail.com \
/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://80x24.org/dtas.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).