From: "Peter Harris" <git@peter.is-a-geek.org>
To: "Karl Hasselström" <kha@treskal.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 2/2] Documentation/git-svn.txt: Fix "git clone" example
Date: Thu, 7 Feb 2008 09:52:27 -0500 [thread overview]
Message-ID: <eaa105840802070652w55570f8ar3a6c4e0d00aa499d@mail.gmail.com> (raw)
In-Reply-To: <20080207143443.GA24687@diana.vm.bytemark.co.uk>
On Feb 7, 2008 9:34 AM, Karl Hasselström <kha@treskal.com> wrote:
> On 2008-02-06 18:45:03 -0500, Peter Harris wrote:
> > satandard layout
>
> Non-satandard spelling.
Oh, the embarrassment.
An email with corrected spelling is on its way.
Peter Harris
next prev parent reply other threads:[~2008-02-07 14:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-06 23:45 [PATCH 2/2] Documentation/git-svn.txt: Fix "git clone" example Peter Harris
2008-02-07 14:34 ` Karl Hasselström
2008-02-07 14:52 ` Peter Harris [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-02-07 14:52 Peter Harris
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=eaa105840802070652w55570f8ar3a6c4e0d00aa499d@mail.gmail.com \
--to=git@peter.is-a-geek.org \
--cc=git@vger.kernel.org \
--cc=kha@treskal.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).