Ok. Yes, it 's kind of tricky. But the `-- ` does both things.
`-- ` looks for the relative path within the current directory
but defaults to the work-tree root if your current directory does not
belong to the repo.
About `git -C `, awesome feature, I love that, but it's not my
point. (and I'm ac
Hi Roberto,
Roberto Eduardo Decurnex Gorosito wrote:
> When passing objects to the `git log`, by just naming them or using
> the `--objects` option, relative paths are evaluated using the current
> working directory instead of the current working tree path.
Why should they be relative to the wor
Sorry, I left the --git-dir out of the example. I do set the --git-dir
(and $GIT_DIR sometimes) too.
It gives the same results. That's why I feels like it shouldn't be
working as it is.
In this specific case (log with object filter) the environment config
is completely ignored.
On Mon, Sep 29, 2
Roberto Eduardo Decurnex Gorosito
writes:
> ~/path$ git --work-tree=~/path/to_repo log README.md
This does not seem to specify GIT_DIR explicitly (either with the
$GIT_DIR environment variable or the --git-dir option), so I would
assume that you are sitting in a directory that has ".git/"
subdir
When passing objects to the `git log`, by just naming them or using
the `--objects` option, relative paths are evaluated using the current
working directory instead of the current working tree path.
Even the error message is clearly wrong.
"unknown revision or path not in the working tree."
E
5 matches
Mail list logo
