From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Stefan Christ <contact@stefanchrist.eu>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Documenation: fmt-merge-msg: fix markup in example
Date: Fri, 28 Oct 2016 06:24:03 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.20.1610280623400.524@localhost.localdomain> (raw)
In-Reply-To: <1477648886-12096-1-git-send-email-contact@stefanchrist.eu>
"Documenation"?
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next prev parent reply other threads:[~2016-10-28 10:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-28 10:01 [PATCH] Documenation: fmt-merge-msg: fix markup in example Stefan Christ
2016-10-28 10:24 ` Robert P. J. Day [this message]
2016-10-28 15:07 ` [PATCH v2] Documentation: " Stefan Christ
2016-10-28 11:08 ` [PATCH] Documenation: " Jeff King
2016-10-28 15:15 ` Junio C Hamano
2016-10-28 23:19 ` Stefan Christ
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=alpine.LFD.2.20.1610280623400.524@localhost.localdomain \
--to=rpjday@crashcourse.ca \
--cc=contact@stefanchrist.eu \
--cc=git@vger.kernel.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).