From: Pete Wyckoff <pw@padd.com>
To: Frans Klaver <fransklaver@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [RFC PATCH] git-p4: introduce asciidoc documentation
Date: Sun, 4 Dec 2011 16:49:03 -0500 [thread overview]
Message-ID: <20111204214903.GA17331@arf.padd.com> (raw)
In-Reply-To: <op.v5zh6udk0aolir@keputer>
fransklaver@gmail.com wrote on Sun, 04 Dec 2011 22:33 +0100:
> >+Clone options
> >+~~~~~~~~~~~~~
> >+These options can used in an initial 'clone', along with the 'sync
>
> s/can used/can be used/
Thanks for checking. I'll roll it in with the next submission.
-- Pete
next prev parent reply other threads:[~2011-12-04 21:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-03 23:53 [RFC PATCH] git-p4: introduce asciidoc documentation Pete Wyckoff
2011-12-04 21:33 ` Frans Klaver
2011-12-04 21:49 ` Pete Wyckoff [this message]
2011-12-07 9:46 ` Luke Diamand
2011-12-07 15:36 ` Pete Wyckoff
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=20111204214903.GA17331@arf.padd.com \
--to=pw@padd.com \
--cc=fransklaver@gmail.com \
--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).