From: Andy Whitcroft <apw@shadowen.org>
To: Git Mailing List <git@vger.kernel.org>, Junio C Hamano <junkio@cox.net>
Subject: git pickaxe -- problems with relative filenames
Date: Thu, 02 Nov 2006 03:21:22 +0000 [thread overview]
Message-ID: <45496432.80503@shadowen.org> (raw)
We seem to have a difference in the handling of relative filenames
within a repository between git blame and git pickaxe. Specifically git
pickaxe seems to always require names as if it were run in the top of
the project:
apw@pinky$ pwd
/home/apw/git/git/Documentation
apw@pinky$ git blame git.txt | head -2
7984eabe (Sebastian Kuzminsky 2005-05-19 10:24:54 -0600 1) git(7)
2cf565c5 (David Greaves 2005-05-10 22:32:30 +0100 2) ======
apw@pinky$ git pickaxe git.txt | head -2
fatal: cannot stat path git.txt: No such file or directory
apw@pinky$ git pickaxe Documentation/git.txt | head -2
7984eabe (Sebastian Kuzminsky 2005-05-19 10:24:54 -0600 1) git(7)
2cf565c5 (David Greaves 2005-05-10 22:32:30 +0100 2) ======
This seems inconsistent? Is this expected behaviour?
next reply other threads:[~2006-11-02 3:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-02 3:21 Andy Whitcroft [this message]
2006-11-02 7:22 ` [PATCH] git-pickaxe: look for files relative to current path Jeff King
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=45496432.80503@shadowen.org \
--to=apw@shadowen.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).