git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Li Hong <lihong.hi@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: git@vger.kernel.org
Subject: Re: [RFC] 'git cat-file' needs a better design on its option  interface
Date: Fri, 25 Sep 2009 10:33:21 +0800	[thread overview]
Message-ID: <3a3680030909241933g5ac48496ic9673030de81898c@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.01.0909241021120.3303@localhost.localdomain>

2009/9/25 Linus Torvalds <torvalds@linux-foundation.org>:
>
>
> On Thu, 24 Sep 2009, Li Hong wrote:
>>
>> When using 'git cat-file' recently, I find its option interface is somewhat
>> inconvenient or mistakenly-designed.
>
> You likely shouldn't use 'cat-file' at all. Have you looked at 'git show'?
> That's the command meant for human beings.
>
> 'git cat-file' is really really low-level plumbing. Humans should
> generally never use it. It's one of the original git commands (it was
> literally in the original git commit), and it does some really low-level
> stuff that is good for scripting but not for any normal use.
>
>                Linus
>

Yes, I know 'git show' and use it mostly. I just think the interface
of 'cat-file'
is not well designed even used by other scripts or porcelains. But from another
respect, it doesn't really annoy normal users much and we should retain
backwards compatibility. So I give up.

Thanks for all your feedbacks.

-Li Hong

      parent reply	other threads:[~2009-09-25  2:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-24 15:04 [RFC] 'git cat-file' needs a better design on its option interface Li Hong
2009-09-24 16:48 ` Jeff King
2009-09-24 17:23 ` Linus Torvalds
2009-09-24 19:21   ` Matthieu Moy
2009-09-24 19:30     ` Nicolas Pitre
2009-09-25  2:33   ` Li Hong [this message]

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=3a3680030909241933g5ac48496ic9673030de81898c@mail.gmail.com \
    --to=lihong.hi@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=torvalds@linux-foundation.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.
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).