From: Michael J Gruber <git@drmicha.warpmail.net>
To: "McAuley, Ben" <Ben.McAuley@sungard.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [BUG] GIT_INDEX environment variable ignored?
Date: Thu, 8 Oct 2015 09:56:17 +0200 [thread overview]
Message-ID: <561621A1.8090609@drmicha.warpmail.net> (raw)
In-Reply-To: <3316005380861448B5340D39CF27A7242F2375BE@us-voo-mb04.internal.sungard.corp>
McAuley, Ben venit, vidit, dixit 08.10.2015 06:48:
> Hello,
>
> I was trying to use multiple indexes earlier, and ran into an issue which I've summarised into a test case:
>
> $ git init
> $ touch file1 && git add file1 && git commit -m "file1"
> $ git branch release
> $ touch file2 && git add file2 && git commit -m "file2"
> $ cp .git/index .git/indexMaster
> $ git checkout release
> $ touch file3 && git add file3 && git commit -m "file3"
>
> I then ran ls-files with the --stage option to look at what the index contains.
> As expected file1 and file3 are present, we're on the 'release' branch still.
>
> $ git ls-files --stage
> 100644 e69de29bb2d1d6434b8b29ae775ad8c2e48c5391 0 file1
> 100644 e69de29bb2d1d6434b8b29ae775ad8c2e48c5391 0 file3
>
> However when I run the same command again, this time using the
> GIT_INDEX env variable to provide the index I previously saved on master,
> I don't see file2 like I'd expect...
>
> $ GIT_INDEX=.git/indexMaster git ls-files --stage
> 100644 e69de29bb2d1d6434b8b29ae775ad8c2e48c5391 0 file1
> 100644 e69de29bb2d1d6434b8b29ae775ad8c2e48c5391 0 file3
>
> Is this something going wrong, or am I misunderstanding the role of the index/GIT_INDEX variable?
>
> Replicated on 2.5.0.windows.1 and 2.6.1 (Linux).
Maybe try GIT_INDEX_FILE instead of GIT_INDEX? ;)
Michael
prev parent reply other threads:[~2015-10-08 7:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-08 4:48 [BUG] GIT_INDEX environment variable ignored? McAuley, Ben
2015-10-08 7:28 ` Matthieu Moy
2015-10-08 7:56 ` Michael J Gruber [this message]
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=561621A1.8090609@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=Ben.McAuley@sungard.com \
--cc=git@vger.kernel.org \
/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).