From: Andreas Ericsson <ae@op5.se>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Inconsistencies with git log
Date: Thu, 08 Nov 2007 01:16:47 +0100 [thread overview]
Message-ID: <4732556F.30105@op5.se> (raw)
In-Reply-To: <9e4733910711071609t3e5412f1mf02e501b2d820bb3@mail.gmail.com>
Jon Smirl wrote:
> On 11/7/07, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
>> It is consistent, when you realise that the path arguments are interpreted
>> relative to the project root.
>
> Then why doesn't this work?
>
> jonsmirl@terra:~/mpc5200b$ git log Documentation
> all the log for Documentation....
> jonsmirl@terra:~/mpc5200b$ cd Documentation
> jonsmirl@terra:~/mpc5200b/Documentation$ git log Documentation
> fatal: ambiguous argument 'Documentation': unknown revision or path
> not in the working tree.
> Use '--' to separate paths from revisions
> jonsmirl@terra:~/mpc5200b/Documentation$
>
Because your current working directory, relative to the project root, is
prepended to the path you're in, so git sees "Documentation/Documentation".
I'm unsure why
cd Documentation; git log -- /Documentation
doesn't do the trick though. I know that particular trick used to work for
some other command a while back anyways.
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
next prev parent reply other threads:[~2007-11-08 8:24 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-07 22:15 Inconsistencies with git log Jon Smirl
2007-11-07 22:42 ` Johannes Schindelin
2007-11-07 22:45 ` Jon Smirl
2007-11-07 22:58 ` Johannes Schindelin
2007-11-07 23:03 ` Jon Smirl
2007-11-07 23:11 ` Johannes Schindelin
2007-11-07 23:16 ` Jon Smirl
2007-11-07 23:29 ` Jon Smirl
2007-11-08 0:04 ` Johannes Schindelin
2007-11-08 0:09 ` Jon Smirl
2007-11-08 0:16 ` Andreas Ericsson [this message]
2007-11-08 0:35 ` Johannes Schindelin
2007-11-09 15:54 ` Linus Torvalds
2007-11-09 17:20 ` Jon Smirl
2007-11-09 17:38 ` Linus Torvalds
2007-11-09 17:53 ` Linus Torvalds
2007-11-09 18:04 ` Jon Smirl
2007-11-09 18:14 ` Linus Torvalds
2007-11-09 18:22 ` Peter Baumann
2007-11-09 18:35 ` Junio C Hamano
2007-11-09 18:37 ` Jakub Narebski
2007-11-09 18:39 ` Peter Baumann
2007-11-09 18:36 ` Linus Torvalds
2007-11-09 17:41 ` Jakub Narebski
2007-11-08 9:24 ` Wincent Colaiuta
2007-11-08 18:28 ` Daniel Barkalow
2007-11-07 23:19 ` Brian Gernhardt
2007-11-07 23:31 ` David Symonds
2007-11-08 0:09 ` Johannes Schindelin
2007-11-08 0:14 ` David Symonds
2007-11-08 0:52 ` Brian Gernhardt
2007-11-08 0:10 ` [PATCH 1/2] Makefile: wt-status.h is also a lib header Johannes Schindelin
2007-11-08 0:11 ` Inconsistencies with git log Andreas Ericsson
2007-11-08 8:29 ` Peter Baumann
2007-11-08 13:16 ` David Symonds
2007-11-08 13:40 ` Andreas Ericsson
2007-11-08 21:21 ` Alex Riesen
2007-11-08 21:23 ` Alex Riesen
2007-11-08 0:12 ` [PATCH 2/2] git status: show relative paths when run in a subdirectory Johannes Schindelin
2007-11-08 0:53 ` David Symonds
2007-11-08 1:00 ` Johannes Schindelin
2007-11-08 8:26 ` Junio C Hamano
2007-11-09 15:30 ` [PATCH REPLACEMENT for " Johannes Schindelin
2007-11-10 12:08 ` Michel Marti
2007-11-10 14:10 ` Johannes Schindelin
2007-11-08 9:19 ` Inconsistencies with git log Wincent Colaiuta
2007-11-10 22:51 ` Miles Bader
2007-11-07 23:00 ` David Symonds
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=4732556F.30105@op5.se \
--to=ae@op5.se \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=jonsmirl@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.