From: Martin Langhoff <martin.langhoff@gmail.com>
To: Junio C Hamano <junkio@cox.net>
Cc: Josef Weidendorfer <Josef.Weidendorfer@gmx.de>, git@vger.kernel.org
Subject: Re: Convention for help in git commands?
Date: Wed, 26 Oct 2005 09:24:48 +1300 [thread overview]
Message-ID: <46a038f90510251324s50911b88pb5eabb304644bcad@mail.gmail.com> (raw)
In-Reply-To: <7vfyqpe87x.fsf@assigned-by-dhcp.cox.net>
On 10/26/05, Junio C Hamano <junkio@cox.net> wrote:
> > * For commands which need at least one argument, the usage
> > is also printed, if the command is run without argument
>
> This is slightly debatable. I'd rather see it error out for one
> thing, and we might want to do a sane default given no arguments
> later.
This could lead to subtle bugs when git is used by porcelains. If
there are going to be changes in default behaviours, let's have them
soon-ish ;-)
cheers,
martin
next prev parent reply other threads:[~2005-10-25 20:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-25 13:08 Convention for help in git commands? Josef Weidendorfer
2005-10-25 18:56 ` Junio C Hamano
2005-10-25 20:24 ` Martin Langhoff [this message]
2005-10-25 21:35 ` Josef Weidendorfer
2005-10-25 22:07 ` Martin Langhoff
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=46a038f90510251324s50911b88pb5eabb304644bcad@mail.gmail.com \
--to=martin.langhoff@gmail.com \
--cc=Josef.Weidendorfer@gmx.de \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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