From: A Large Angry SCM <gitzilla@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Alex Riesen <raa.lkml@gmail.com>,
linux@horizon.com, Junio C Hamano <junkio@cox.net>,
git@vger.kernel.org
Subject: Re: [PATCH] git-rev-list --help anywhere
Date: Sun, 19 Feb 2006 11:40:14 -0800 [thread overview]
Message-ID: <43F8C99E.7080703@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0602192023270.11855@wbgn013.biozentrum.uni-wuerzburg.de>
Johannes Schindelin wrote:
> Hi,
>
> can someone please enlighten me why you need to see the usage, when you
> cannot execute the command anyway?
>
> Puzzled,
> Dscho
How about so that you can find the options needed to run the command in
another window where it will work.
next prev parent reply other threads:[~2006-02-19 19:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-19 11:26 [PATCH] git-rev-list --help anywhere linux
2006-02-19 18:39 ` Alex Riesen
2006-02-19 19:25 ` Johannes Schindelin
2006-02-19 19:39 ` linux
2006-02-19 19:40 ` A Large Angry SCM [this message]
2006-02-20 5:52 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2006-02-19 11:09 Alex Riesen
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=43F8C99E.7080703@gmail.com \
--to=gitzilla@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=linux@horizon.com \
--cc=raa.lkml@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).