From: Philip Oakley <philipoakley@iee.email>
To: Eugen Konkov <kes-kes@yandex.ru>, Git Mailing List <git@vger.kernel.org>
Subject: Re: Ambigious messages (sparse checkout)
Date: Sat, 31 Jul 2021 13:31:26 +0100 [thread overview]
Message-ID: <5b0e38b0-7060-239e-5adf-b751a67f6646@iee.email> (raw)
In-Reply-To: <644619140.20210731114616@yandex.ru>
Others may have mistaken this for spam - I nearly did.
On 31/07/2021 09:46, Eugen Konkov wrote:
> $ git checkout 51c7d41b82b5b
> error: Your local changes to the following files would be overwritten by checkout:
> lib/Mojo/IOLoop/Stream.pm
> Please commit your changes or stash them before you switch branches.
> Aborting
> $ git checkout lib/Mojo/IOLoop/Stream.pm
> error: pathspec 'lib/Mojo/IOLoop/Stream.pm' did not match any file(s) known to git
>
> $ git add lib/Mojo/IOLoop/Stream.pm
> The following pathspecs didn't match any eligible path, but they do match index
> entries outside the current sparse checkout:
I strongly suspect it's a sparse checkout issue, given this message.
Others may be able to help better than I.
> lib/Mojo/IOLoop/Stream.pm
> hint: Disable or modify the sparsity rules if you intend to update such entries.
> hint: Disable this message with "git config advice.updateSparsePath false"
>
> $ git --version
> git version 2.32.0
>
> Here I do not understand how to checkout to different commit
> or how to commit the subject file
>
> It would be nice to show hint about how to exlude this file from unindex
>
>
> --
> Best regards,
> Eugen Konkov
>
--
Philip
next prev parent reply other threads:[~2021-07-31 12:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-31 8:46 Ambigious messages Eugen Konkov
2021-07-31 12:31 ` Philip Oakley [this message]
2021-08-01 0:27 ` Elijah Newren
2021-08-02 13:48 ` Eugen Konkov
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=5b0e38b0-7060-239e-5adf-b751a67f6646@iee.email \
--to=philipoakley@iee.email \
--cc=git@vger.kernel.org \
--cc=kes-kes@yandex.ru \
/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.