From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH] Make Documentation (somehwat more) consistent
Date: Sun, 11 Jun 2006 23:04:09 +0200 [thread overview]
Message-ID: <e6i0fl$ui0$1@sea.gmane.org> (raw)
In-Reply-To: 11500582752231-git-send-email-vonbrand@inf.utfsm.cl
Horst H. von Brand wrote:
> Fix the quoting of the command names, files, etc
> The commands should be used as 'git foo', not 'git-foo'
> Fix some messed up grammar and typing
Commands are used as 'git foo' from command line (user commands,
porcelanish), but in scripts usually used as 'git-foo', and you ask for
'man git-foo'.
--
Jakub Narebski
Warsaw, Poland
prev parent reply other threads:[~2006-06-11 21:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-11 20:37 [PATCH] The name of the hash is SHA-1, use it consistently in Documentation Horst H. von Brand
2006-06-11 20:37 ` [PATCH] Make Documentation (somehwat more) consistent Horst H. von Brand
2006-06-11 21:04 ` Jakub Narebski [this message]
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='e6i0fl$ui0$1@sea.gmane.org' \
--to=jnareb@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).