Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: git@vger.kernel.org, Aneesh Kumar <aneesh.kumar@gmail.com>
Subject: Re: blameview and file contents
Date: Tue, 30 Jan 2007 00:30:25 -0800	[thread overview]
Message-ID: <7vveio5332.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20070130072910.GB32640@spearce.org> (Shawn O. Pearce's message of "Tue, 30 Jan 2007 02:29:10 -0500")

"Shawn O. Pearce" <spearce@spearce.org> writes:

> Aneesh Kumar <aneesh.kumar@gmail.com> wrote:
>> See i said that there should be a simple way. Can we get this
>> documented in git-cat-file man page
>
> Well, this isn't the git-cat-file man page, but we do suggest people
> use `git show HEAD:foo.c` to get foo.c from HEAD in an interactive
> setting.  The git-show manpage refers people to git-rev-parse,
> which has the following:
>
> 	* A suffix ':' followed by a path; this names the blob or tree
> 	  at the given path in the tree-ish object named by the part
> 	  before the colon.
> ...
> But if you submit a documentation update to git-cat-file's manpage
> that points off to the same section of git-rev-parse, folks may
> appreciate it.  :-)

My feeling is that adding "See SPECIFYING REVISIONS section" to
Porcelain documentation is a very good idea, but unwanted
baggage for plumbing descriptions if added everywhere.  The
target audience of the latter is supposed to know what "object
name" is, so:

 <object>::
-	The sha1 identifier of the object.
+	The name of the object to show.

should be sufficient.

      reply	other threads:[~2007-01-30  8:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-30  6:46 blameview and file contents Aneesh Kumar
2007-01-30  6:54 ` Shawn O. Pearce
2007-01-30  7:22   ` Aneesh Kumar
2007-01-30  7:29     ` Shawn O. Pearce
2007-01-30  8:30       ` Junio C Hamano [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=7vveio5332.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=aneesh.kumar@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=spearce@spearce.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