From: Eric Sunshine <sunshine@sunshineco.com>
To: Fredrik Gustafsson <iveqy@iveqy.com>
Cc: Git List <git@vger.kernel.org>, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] Document .git/modules
Date: Sun, 9 Jun 2013 06:59:17 -0400 [thread overview]
Message-ID: <CAPig+cTHFcvWyoQMConxRTgEz4pq4_3Y-abFp8xAPjsdHniQ8Q@mail.gmail.com> (raw)
In-Reply-To: <1370774269-3258-1-git-send-email-iveqy@iveqy.com>
On Sun, Jun 9, 2013 at 6:37 AM, Fredrik Gustafsson <iveqy@iveqy.com> wrote:
> A note in the begging of this document describe the behavior already.
s/begging/beginning/
s/describe/describes/
> This patch just add where to find the repositories.
s/add/adds/
> Signed-off-by: Fredrik Gustafsson <iveqy@iveqy.com>
next prev parent reply other threads:[~2013-06-09 10:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-09 10:37 [PATCH] Document .git/modules Fredrik Gustafsson
2013-06-09 10:59 ` Eric Sunshine [this message]
2013-06-09 11:11 ` Fredrik Gustafsson
2013-06-09 11:13 ` Fredrik Gustafsson
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=CAPig+cTHFcvWyoQMConxRTgEz4pq4_3Y-abFp8xAPjsdHniQ8Q@mail.gmail.com \
--to=sunshine@sunshineco.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=iveqy@iveqy.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).