From: linux@horizon.com
To: Johannes.Schindelin@gmx.de, raa.lkml@gmail.com
Cc: git@vger.kernel.org, junkio@cox.net, linux@horizon.com
Subject: Re: [PATCH] git-rev-list --help anywhere
Date: 19 Feb 2006 14:39:40 -0500 [thread overview]
Message-ID: <20060219193940.7493.qmail@science.horizon.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0602192023270.11855@wbgn013.biozentrum.uni-wuerzburg.de>
> can someone please enlighten me why you need to see the usage, when you
> cannot execute the command anyway?
Because you're writing a script, or explaining it to someone over
the phone, or writing shell autocompletion macros, otherwise using
it in some kind of delayed or deferred way.
These ain't no steenkin GUI tools; they can be used in more ways
that typed interactively for immediate execution.
(Have you ever noticed how all the GUI people have rediscovered the
concept of a pathname and a single-character directory separator when
explaining how to navigate a menu/dialog maze? The character '>' seems
to be popular.
Go to menu A
Then go to submenu B
Then select item C to open a dialog
Then go to tab D of that dialog.
Then hit the "Advanced options" button
Then select tab E of that dialog
Then select option F
How exactly is this is an improvement over A/B/C/D/Advanced options/E/F?)
next prev parent reply other threads:[~2006-02-19 19:39 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 [this message]
2006-02-19 19:40 ` A Large Angry SCM
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=20060219193940.7493.qmail@science.horizon.com \
--to=linux@horizon.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--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).