git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH v3] Support ent:relative_path
Date: Sat, 05 May 2007 03:11:27 +0200	[thread overview]
Message-ID: <f1glk1$6qh$1@sea.gmane.org> (raw)
In-Reply-To: 463BD40C.6080909@gmail.com

Dana How wrote:

> Most commands accept relative paths,  but this is
> not true of arguments in ent:path format.  This
> patch makes all of the following git-show commands
> work in the git source tree (not just the first):
>
>  % cd xdiff
>  % git-show v1.5.2-rc0:xdiff/xemit.h
>  % git-show v1.5.2-rc0:./xemit.h
>  % git-show v1.5.2-rc0:../sha1_name.c
> 
> It also adds ent:?string as a synonym for ent:/string .
> This makes the following changes possible later:
> ent:/path is an absolute path and ent:path is relative.

First, we now usually use 'tree-ish' or 'treeish', not 'ent'.
Second, it is ':/<text>', not '<tree-ish>:/<text>'

git-rev-parse(1):

 * A colon, followed by a slash, followed by a text: this names
   a commit whose commit message starts with the specified text.
   This name returns the youngest matching commit which is
   reachable from any ref.  If the commit message starts with a
   '!', you have to repeat that;  the special sequence ':/!',
   followed by something else than '!' is reserved for now.

-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git

  reply	other threads:[~2007-05-05  1:11 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-05  0:47 [PATCH v3] Support ent:relative_path Dana How
2007-05-05  1:11 ` Jakub Narebski [this message]
2007-05-05  1:29 ` Johannes Schindelin
2007-05-05  3:30   ` Shawn O. Pearce
2007-05-05 19:32     ` Martin Waitz
2007-05-05 20:17       ` Junio C Hamano
2007-05-05 21:18         ` Martin Waitz
2007-05-06  0:59           ` Johannes Schindelin
2007-05-06 18:52             ` Martin Waitz
2007-05-06 23:09               ` Johannes Schindelin
2007-05-05 20:37       ` Alex Riesen
2007-05-05  3:38   ` Junio C Hamano
2007-05-05  6:46     ` Dana How
2007-05-05  8:03       ` Alex Riesen
2007-05-05 14:39       ` Johannes Schindelin
2007-05-06  6:38         ` Junio C Hamano
2007-05-06 15:14           ` Johannes Schindelin
2007-05-06 17:35             ` Junio C Hamano
2007-05-06 23:12               ` Johannes Schindelin
2007-05-07  0:18                 ` Junio C Hamano
2007-05-07  0:37                   ` Dana How

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='f1glk1$6qh$1@sea.gmane.org' \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.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).