From: "JunkYardMail1" <JunkYardMail1@Frontier.com>
To: <git@vger.kernel.org>
Subject: Sparse Checkout Trouble (2.5.0)
Date: Tue, 21 Jan 2020 16:42:02 -0800 [thread overview]
Message-ID: <062301d5d0bc$c3e17760$4ba46620$@Frontier.com> (raw)
I have a shallow repository clone and using sparse-checkout of just a
handful of directories. When I upgraded from git version 2.24.1 to 2.25.0
some files not in the sparse-checkout were staged to be deleted. The
directory path of these files contain the Windows reserved name of "prn".
Ex: "japanese/prn/. . ." Unable to un-stage these files and reset the
changes.
.git/inof/Sparse-checkout:
!/*/
/*/directory-*/
Reverting back to the previous version (2.24.1) allowed to un-stage the
files and reset the changes.
next reply other threads:[~2020-01-22 0:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-22 0:42 JunkYardMail1 [this message]
2020-01-22 1:19 ` Sparse Checkout Trouble (2.5.0) Derrick Stolee
2020-01-22 2:06 ` JunkYardMail1
2020-01-24 15:40 ` Derrick Stolee
2020-01-25 20:59 ` Elijah Newren
2020-01-26 14:09 ` Derrick Stolee
2020-01-28 5:21 ` Elijah Newren
2020-01-28 20:47 ` Derrick Stolee
2020-01-29 15:30 ` Johannes Schindelin
2020-01-29 15:40 ` Derrick Stolee
2020-01-29 16:31 ` Derrick Stolee
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='062301d5d0bc$c3e17760$4ba46620$@Frontier.com' \
--to=junkyardmail1@frontier.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).