git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Eric Sunshine <sunshine@sunshineco.com>
To: Sergii Shkarnikov <sergii.shkarnikov@globallogic.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: Possible bug with git restore
Date: Fri, 14 Aug 2020 18:41:51 -0400	[thread overview]
Message-ID: <CAPig+cSCd_8YB90sypTe1bHMQhPgo+Tr2PHNucdqfCpEe+Dosg@mail.gmail.com> (raw)
In-Reply-To: <CAFvH=vsWyX79j-9pyC5gpxGu8rRxYyrXwywHjh-_T2opHjT8Xg@mail.gmail.com>

On Wed, Aug 12, 2020 at 2:51 PM Sergii Shkarnikov
<sergii.shkarnikov@globallogic.com> wrote:
>     I tried to restore a couple of files from an earlier commit
> running the restore command with a wildcard:
>
>     git restore -s HEAD~ -- */filename.*
>
>     In my work tree those are .cpp and .hpp files stored in different folders.
>     Both files were deleted (and got (delete) status).
>     Running this command without wildcards for each file separately
> works as expected.

Thanks for the report. Can you provide a complete recipe in the form
of shell command to make this happen so others can reproduce the
behavior? Doing so will help track down the issue. Also, since this is
Windows, do the cases of the filenames in the referenced commit match
the cases actually on the filesystem (and have the cases changed
between commits)?

  reply	other threads:[~2020-08-14 22:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-12 18:51 Possible bug with git restore Sergii Shkarnikov
2020-08-14 22:41 ` Eric Sunshine [this message]
2020-08-20 12:59   ` Sergii Shkarnikov
2020-08-20 13:40     ` Jeff King
2020-08-20 17:48       ` René Scharfe
2020-08-20 18:27         ` Jeff King
2020-08-22  8:57           ` [PATCH] checkout, restore: make pathspec recursive René Scharfe
2020-08-24 20:21             ` Jeff King
2020-08-22 10:29           ` Possible bug with git restore René Scharfe
2020-08-24 20:25             ` Jeff King
2020-08-22 19:36           ` Junio C Hamano

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAPig+cSCd_8YB90sypTe1bHMQhPgo+Tr2PHNucdqfCpEe+Dosg@mail.gmail.com \
    --to=sunshine@sunshineco.com \
    --cc=git@vger.kernel.org \
    --cc=sergii.shkarnikov@globallogic.com \
    /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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).