git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "James Pickens" <jepicken@gmail.com>
To: "Scott Chacon" <schacon@gmail.com>
Cc: "Junio C Hamano" <gitster@pobox.com>, "Jeff King" <peff@peff.net>,
	git@vger.kernel.org
Subject: Re: [PATCH] Modified the default git help message to be grouped by topic
Date: Tue, 2 Dec 2008 13:11:25 -0700	[thread overview]
Message-ID: <885649360812021211u3d547982i8e1c3070972363e8@mail.gmail.com> (raw)
In-Reply-To: <d411cc4a0812012210h4cb59974sbda71abd2c64f93b@mail.gmail.com>

On Mon, Dec 1, 2008 at 11:10 PM, Scott Chacon <schacon@gmail.com> wrote:
> Hi,
>
> On Mon, Dec 1, 2008 at 5:45 PM, Junio C Hamano <gitster@pobox.com> wrote:
>> If this list is meant to show "the most commonly used" basics, then you
>> can trim the list somewhat.  For example, "rm" and "mv" can be safely
>> discarded, "status" can be replaced with "diff", and "diff" can be removed
>> from "History Commands".
>>
>
> I sent a new patch that removes 'rm' and 'mv' and removes the
> common-cmd.h build process. I did keep the 'status' command, since in
> my personal experience people tend to like having that command.

Even though 'rm' might not be used very often, I think it's an important
enough command that it should not be removed from the 'basics' list.
AFAIK, the only other way to delete a file is 'rm file' followed by 'git
add -u' or 'git commit -a'.  Imagine a git newbie trying to figure that
out.

I'm tempted to say the same thing about 'mv' as well.  And FWIW, I use
'status' a lot more than I use 'diff', so I would vote to keep 'status' in
the list too.

James

  reply	other threads:[~2008-12-02 20:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-01 17:30 [PATCH] Modified the default git help message to be grouped by topic Scott Chacon
2008-12-01 18:32 ` Jeff King
2008-12-02  1:45   ` Junio C Hamano
2008-12-02  6:10     ` Scott Chacon
2008-12-02 20:11       ` James Pickens [this message]
2008-12-02 21:33         ` Boyd Stephen Smith Jr.
2008-12-02 22:55         ` Johannes Schindelin
2008-12-02 23:30           ` Jeff King
2008-12-02 23:39             ` Scott Chacon
2008-12-03  0:10             ` Junio C Hamano
2008-12-03  0:37               ` Jeff King
2008-12-03  0:47               ` Jakub Narebski

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=885649360812021211u3d547982i8e1c3070972363e8@mail.gmail.com \
    --to=jepicken@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=peff@peff.net \
    --cc=schacon@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).