From: Heikki Orsila <shd@modeemi.fi>
To: Jakub Narebski <jnareb@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH] Start conforming code to "git subcmd" style
Date: Sun, 31 Aug 2008 19:37:51 +0300 [thread overview]
Message-ID: <20080831163751.GB28666@jolt.modeemi.cs.tut.fi> (raw)
In-Reply-To: <m38wudr0mq.fsf@localhost.localdomain>
On Sun, Aug 31, 2008 at 02:32:05AM -0700, Jakub Narebski wrote:
> Either "git-rev-list" or "'git rev-list'" is fine; "git rev-list"
> is not, as it requires careful reading to notice which part is
> proposed git command, and which the rest of message.
I would go for "'git rev-list'". I'll use that form in coming patches,
unless there is resistance to this idea.
--
Heikki Orsila
heikki.orsila@iki.fi
http://www.iki.fi/shd
prev parent reply other threads:[~2008-08-31 16:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-30 11:12 [PATCH] Start conforming code to "git subcmd" style Heikki Orsila
2008-08-30 20:49 ` Junio C Hamano
2008-08-31 1:53 ` Christian Couder
2008-08-31 9:32 ` Jakub Narebski
2008-08-31 16:14 ` Junio C Hamano
2008-08-31 16:37 ` Heikki Orsila [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=20080831163751.GB28666@jolt.modeemi.cs.tut.fi \
--to=shd@modeemi.fi \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jnareb@gmail.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).