Re: [PATCH] Support ent:relative_path
- From
- Dana How <danahow@gmail.com>
- Date
- May 5, 2007, 00:52 UTC
- Message-ID
- <56b7f5510705041752o74b59284x872480e4413f83ab@mail.gmail.com>
- In-Reply-To
- <7vy7k4p24s.fsf@assigned-by-dhcp.cox.net>
On 5/4/07, Junio C Hamano <junkio@cox.net> wrote:
Show 11 quoted lines
> Jakub Narebski <jnareb@gmail.com> writes: > > I'm not sure about "<tree-ish>:<path>" with <path> being relative by > > default. For me it is <path> in <tree-ish> (like in > > "git-ls-tree -r <tree-ish>" result). > > That's right (and Dscho is also). > > "v1.5.1:git.c" IS "git.c that appears at the toplevel of > v1.5.1's tree." > > Ok, for now let's forget about this relative stuff.
Hmm, most of the work I do in the parts of our perforce repository I want to convert to git is far enough down that the paths have 6 in-repo path components. I don't want to type all those when I want to fetch an older version with git-show. Everything I do is relative. In fact, I think perforce supports typing absolute paths, (using an 8-character prefix!) but I have never used it, nor would I if it were shorter.
-- Dana L. How danahow@gmail.com +1 650 804 5991 cell