From: Kevin Daudt <me@ikke.info>
To: Sam Partington <sam@whiteoctober.co.uk>
Cc: git@vger.kernel.org
Subject: Re: Bug when stashing previously-ignored file plus associated .gitignore change
Date: Mon, 14 Aug 2017 06:47:56 +0200 [thread overview]
Message-ID: <20170814044756.GA8587@alpha.vpn.ikke.info> (raw)
In-Reply-To: <CAPuLQgNq_7Kdeio-59cbDjZ5mWC1VRd_1_KK33Gbka9KJ13vfQ@mail.gmail.com>
On Fri, Aug 11, 2017 at 04:55:38PM +0100, Sam Partington wrote:
> Hi there,
>
> I'm running git 2.7.4 on Ubuntu 16.04. I've found a couple of
> problems when "un-ignoring" files in tandem with git stash.
>
> Here's how to reproduce:
>
> Say you have a project using git, with a .gitignore file which
> contains the following line:
>
> bin/*
>
> You can then see the problems by doing this:
>
> $ touch bin/mynewfile # this file will be ignored at this point >
> and then updating .gitignore to look like this (adding that second line):
>
> bin/*
> !bin/mynewfile
>
> So far, so good; the new file is no longer ignored.
>
> But now, try stashing the changes and including untracked files in the stash:
>
> $ git stash save -u
>
> Here's the first problem, bin/mynewfile is still there:
>
> $ ls bin/mynewfile
> bin/mynewfile
>
> But you'd expect it to not be there and be in the stash, I think.
> This is what would normally happen with the untracked-files option for
> git stash.
>
> This leads to the second problem - you can't now pop the stash:
>
> $ git stash pop
> bin/mynewfile already exists, no checkout
> Could not restore untracked files from stash
>
> If you want to apply the stash, you have to remove the file:
>
> $ rm bin/mynewfile
> $ git stash pop # this works, and re-creates bin/mynewfile
>
> This is quite an unusual edge case, but I have hit it two or three
> times now and so thought it worth reporting, but I'll understand if
> it's deemed not worth fixing!
>
> Do let me know if you need any more information from me here.
>
> Thanks
> Sam
>
> PS Sorry for the lack of formatting - I'm sending this as plain text
> as my original HTML emails was rejected as possible spam by your
> mailserver.
>
> Sam Partington
> Senior Developer
>
Hello Sam,
Is it the case that you did not commit the addition of '!bin/mynewfile'
yet? I suspect that by running git stash save -u, you also are stashing
this addition to the .gitigore file. Can you confirm this?
Kevin
next prev parent reply other threads:[~2017-08-14 4:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-11 15:55 Bug when stashing previously-ignored file plus associated .gitignore change Sam Partington
2017-08-11 17:14 ` [PATCH] stash: clean untracked files before reset Nicolas Morey-Chaisemartin
2017-08-11 22:11 ` Junio C Hamano
2017-08-14 4:47 ` Kevin Daudt [this message]
2017-08-14 7:38 ` Bug when stashing previously-ignored file plus associated .gitignore change Sam Partington
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=20170814044756.GA8587@alpha.vpn.ikke.info \
--to=me@ikke.info \
--cc=git@vger.kernel.org \
--cc=sam@whiteoctober.co.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.
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).