From: Florian Weimer <fweimer@redhat.com>
To: Joshua Lamusga <joshlamusga@gmail.com>, git@vger.kernel.org
Subject: Re: Deleting a branch after merging it results in "there may be uncommitted changes"
Date: Tue, 17 Oct 2017 14:24:08 +0200 [thread overview]
Message-ID: <fe4063db-c917-2661-2b5a-17c0d226f49a@redhat.com> (raw)
In-Reply-To: <CA+bN42rdGATo-T-ibWRMvXsKJwgX6Lp_xSM+MEQdc3tOejshog@mail.gmail.com>
On 10/05/2017 05:04 AM, Joshua Lamusga wrote:
> Anyway, I follow a very simple merging model for this one-person
> project. Recently, I made a new local branch off of develop called
> feature-printing. After checking out feature-printing, making my
> changes, and committing changes, I merged it with develop. I then
> immediately tried to delete feature-printing, which resulted in a
> prompt asking if I was sure since it might contain uncommitted
> changes. Though I've seen this problem many times on the internet, I
> haven't seen it in the context of literally just merging. There are 0
> steps between merging and deleting the old branch.
What's the exact warning? It seems unlikely that your Git interface
would complain about *uncommitted* changes in this context.
> All of this is done in Visual Studio's GUI for Git. Any ideas?
Maybe ask on a Visual Studio forum instead, in case this is something
generated by the front end?
Florian
prev parent reply other threads:[~2017-10-17 12:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-05 3:04 Deleting a branch after merging it results in "there may be uncommitted changes" Joshua Lamusga
2017-10-17 12:24 ` Florian Weimer [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=fe4063db-c917-2661-2b5a-17c0d226f49a@redhat.com \
--to=fweimer@redhat.com \
--cc=git@vger.kernel.org \
--cc=joshlamusga@gmail.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.
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).