On Wed, Feb 18, 2015 at 04:38:55PM -0500, Eric Frederich wrote:
> Also, how would I go about detecting untracked files the way status does?
> There is no way to specify a HEAD per git command using switches or
> environment variables.
> I can't change the HEAD of the Git repo because other process
On Wed, Feb 18, 2015 at 1:38 PM, Eric Frederich
wrote:
> Could you elaborate on "you can just refresh the index before each diff"
> What command would I use to do this?
"update-index --refresh", perhaps?
> Also, how would I go about detecting untracked files the way status does?
"ls-files"?
--
On Wed, Feb 18, 2015 at 1:32 PM, Jeff King wrote:
> On Wed, Feb 18, 2015 at 01:27:50PM -0500, Eric Frederich wrote:
>
> If you can persist the index file for each working tree, this will be
> much faster in the long run, too (you can just refresh the index before
> each diff, which means that git
Thanks Jeff.
I recognize your picture from here...
http://git.661346.n2.nabble.com/push-race-td7569254.html
... which helped me figure out how two processes trying to update a
ref at the same time works out.
I will try using a separate GIT_INDEX_FILE for each working tree.
I'm not certain tha
On Wed, Feb 18, 2015 at 01:27:50PM -0500, Eric Frederich wrote:
> My immediate concern is not to fix the documentation but to get some
> sort of status or diff.
> I want to avoid using an index because I want to allow multiple
> processes to do different diffs at the same time.
If you only have o
Thanks for the reply.
My immediate concern is not to fix the documentation but to get some
sort of status or diff.
I want to avoid using an index because I want to allow multiple
processes to do different diffs at the same time.
Right now I can put trees into the repo and get trees out without
usi
Eric Frederich writes:
> This is from "git help diff". It seems to imply that I should be able to do
> it.
> It mentions nothing of the index.
Most of the documentation on early subcommands (and "git diff"
certainly is one of the early subcommands) were written back when
everybody knew that Gi
This is from "git help diff". It seems to imply that I should be able to do it.
It mentions nothing of the index.
git diff [--options] [--] [...]
This form is to view the changes you have in your working
tree relative to the named . You can use HEAD to compare it
with the lates
On Wed, Feb 18, 2015 at 7:06 AM, Eric Frederich
wrote:
> # how can I compare a working directory to a commit without taking the
> index into account?
You don't.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo i
More concise example:
cd /tmp
git clone --bare https://github.com/defnull/bottle.git
mkdir /tmp/bottlecopy
git --git-dir=/tmp/bottle.git --work-tree=/tmp/bottlecopy checkout master .
# this shows no diffs
git --git-dir=/tmp/bottle.git --work-tree=/tmp/bottlecopy diff master
rm /tmp/bottle.git/ind
Some background.
I'm trying to use Git as an object store for trees.
I put trees into the repo and can retrieve them.
I'm having issues with diffing these trees that I retrieve from the repo.
If I use a "git checkout" the diffs seem to work but if I create the
tree myself user lower level ls-tree a
11 matches
Mail list logo
