From: Marc Branchaud <marcnarc@xiplink.com>
To: git@vger.kernel.org
Cc: gitster@pobox.com
Subject: Re: [PATCH] RelNotes: Spelling & grammar fixes.
Date: Fri, 15 Nov 2013 10:26:42 -0500 [thread overview]
Message-ID: <52863D32.4090005@xiplink.com> (raw)
In-Reply-To: <1384448473-25840-1-git-send-email-marcnarc@xiplink.com>
Oops:
Signed-off-by: Marc Branchaud <marcnarc@xiplink.com>
Sorry!
(I have at long last automated s-o-b in my git repo...)
M.
next prev parent reply other threads:[~2013-11-15 15:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-13 23:07 [ANNOUNCE] Git v1.8.5-rc2 Junio C Hamano
2013-11-14 16:47 ` Marc Branchaud
2013-11-18 17:01 ` Junio C Hamano
2013-11-18 18:49 ` Junio C Hamano
2013-11-18 19:42 ` Marc Branchaud
2013-11-14 17:01 ` [PATCH] RelNotes: Spelling & grammar fixes Marc Branchaud
2013-11-15 15:26 ` Marc Branchaud [this message]
2013-11-18 18:42 ` Junio C Hamano
2013-11-18 19:52 ` Marc Branchaud
2013-11-18 20:00 ` Jonathan Nieder
2013-11-18 22:12 ` Junio C Hamano
2013-11-18 19:58 ` Jonathan Nieder
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=52863D32.4090005@xiplink.com \
--to=marcnarc@xiplink.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
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).