git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Sebastian Pipping <webmaster@hartwork.org>
Cc: Thomas Rast <trast@student.ethz.ch>, Git ML <git@vger.kernel.org>
Subject: Re: Parameter --color-words not documented for "git show"
Date: Thu, 20 Jan 2011 13:25:54 -0800	[thread overview]
Message-ID: <7vk4hzqnbx.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <4D389E69.608@hartwork.org> (Sebastian Pipping's message of "Thu\, 20 Jan 2011 21\:43\:21 +0100")

Sebastian Pipping <webmaster@hartwork.org> writes:

> On 01/20/11 21:27, Thomas Rast wrote:
>> Quote from the latter:
>> 
>>        This manual page describes only the most frequently used options.
>
> Okay.  Is that a good a idea?

Yes; the alternative is to list everything.

> Is --abbrev-commit really used more
> frequently with "git show" than --color-words is?

I see this as a not-so-helpful-but-still-interesting question.

It depends on who you are, and if one wants to pick the most often used
ones, that selection may or may not coincide with _your_ usage pattern nor
mine.  The original author apparently thought so, you seem to think
color-words is used a lot more often, and I personally think neither is
used often at all.  So should we swap them, keep things as-is, or remove
both?

We obviously cannot take a poll to update the list every time a new user
starts using git, but it might make sense to review them every once in a
while.

  reply	other threads:[~2011-01-20 21:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-20 19:58 Parameter --color-words not documented for "git show" Sebastian Pipping
2011-01-20 20:27 ` Thomas Rast
2011-01-20 20:43   ` Sebastian Pipping
2011-01-20 21:25     ` Junio C Hamano [this message]
2011-01-20 23:16       ` Nicolas Sebrecht
2011-01-20 23:34         ` Jeff King
2011-01-21  0:05           ` Sebastian Pipping
2011-01-21  0:20             ` Jeff King
2011-01-21  0:27               ` Sebastian Pipping
2011-01-21  6:08           ` Junio C Hamano
2011-01-21 16:16             ` Jeff King
2011-01-21 10:08           ` Maaartin
2011-01-21 16:17             ` Jeff King
2011-01-23 10:35       ` 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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7vk4hzqnbx.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=trast@student.ethz.ch \
    --cc=webmaster@hartwork.org \
    /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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).