From: Rafik E Younan <rafik.arkdev@gmail.com>
To: John Keeping <john@keeping.me.uk>
Cc: git@vger.kernel.org
Subject: Re: index file list files not found in working tree
Date: Tue, 25 Aug 2015 16:50:08 +0200 [thread overview]
Message-ID: <55DC80A0.3060309@gmail.com> (raw)
In-Reply-To: <20150825103214.GH1412@serenity.lan>
On 08/25/2015 12:32 PM, John Keeping wrote:
> On Tue, Aug 25, 2015 at 12:16:43PM +0200, Rafik E Younan wrote:
>> I got a recommendation to use reset --hard. I tried it and it says the
>> HEAD is now at correct commit, but missing files are not restored!
>>
>> I tried `ls-tree --name-only` and it lists missing files and folders,
>> but the actual working tree doesn't have these files and folders.
> Is there any chance that you have enabled sparse checkouts? See the
> documentation at the bottom of git-read-tree(1).
>
>
There was `.git/info/sparse-checkout` file in the local repo, but not in
other cloned repo. I remove the file, the `.git/index` and did reset
--hard, and all seems works now.
Thanks for your help.
Git community rocks!
Regards,
Rafik
prev parent reply other threads:[~2015-08-25 14:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-24 10:34 index file list files not found in working tree Rafik E Younan
2015-08-25 10:16 ` Rafik E Younan
2015-08-25 10:32 ` John Keeping
2015-08-25 14:50 ` Rafik E Younan [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=55DC80A0.3060309@gmail.com \
--to=rafik.arkdev@gmail.com \
--cc=git@vger.kernel.org \
--cc=john@keeping.me.uk \
/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).