From: Anirban Mitra <anirban.m@directi.com>
To: git@vger.kernel.org
Subject: Re: Git stash bug
Date: Fri, 09 Jul 2010 17:45:16 +0530 [thread overview]
Message-ID: <4C3712D4.8020909@directi.com> (raw)
In-Reply-To: <4C36B520.70105@directi.com>
Hi,
Sorry for the last msg. It seems the behavior happened in a different
situation then what I described which now I can't reproduce.
-- Anirban
On Friday 09 July 2010 11:05 AM, Anirban Mitra wrote:
> Hi,
>
> I ran into a git stash bug. I added a new project config file used by
> the IDE in a commit and later reverted the commit. But the same file
> again created by the IDE and now when I use git stash that file
> changes are also stashed. When I try stash pop, it complains that the
> file will be overwritten and aborts.
>
> I did not expect this because I have reverted the commit adding the
> file. Is it intended behaviour? Am I missing something or is this a
> known bug and will be fixed in later releases? I am using Git version
> 1.7.0.4.
>
> -- Anirban
prev parent reply other threads:[~2010-07-09 12:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-09 5:35 Git stash bug Anirban Mitra
2010-07-09 12:15 ` Anirban Mitra [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=4C3712D4.8020909@directi.com \
--to=anirban.m@directi.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).