From: "Boyd Stephen Smith Jr." <bss03@volumehost.net>
To: git@vger.kernel.org
Cc: "James Pickens" <jepicken@gmail.com>,
"Scott Chacon" <schacon@gmail.com>,
"Junio C Hamano" <gitster@pobox.com>, "Jeff King" <peff@peff.net>
Subject: Re: [PATCH] Modified the default git help message to be grouped by topic
Date: Tue, 2 Dec 2008 15:33:41 -0600 [thread overview]
Message-ID: <200812021533.42114.bss03@volumehost.net> (raw)
In-Reply-To: <885649360812021211u3d547982i8e1c3070972363e8@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1254 bytes --]
On Tuesday 02 December 2008, "James Pickens" <jepicken@gmail.com> wrote
about 'Re: [PATCH] Modified the default git help message to be grouped by
topic':
>On Mon, Dec 1, 2008 at 11:10 PM, Scott Chacon <schacon@gmail.com> wrote:
>> 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.
x2 to all of both paragraphs, except that I'm not just "tempted"; I do say
that mv should be kept.
--
Boyd Stephen Smith Jr. ,= ,-_-. =.
bss03@volumehost.net ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-'
http://iguanasuicide.org/ \_/
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-12-02 21:35 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
2008-12-02 21:33 ` Boyd Stephen Smith Jr. [this message]
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=200812021533.42114.bss03@volumehost.net \
--to=bss03@volumehost.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jepicken@gmail.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).