From: Jeff King <peff@peff.net>
To: Nick Hunt <nhunt11@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Potential git bug
Date: Mon, 19 Mar 2018 16:16:44 -0400 [thread overview]
Message-ID: <20180319201644.GA25618@sigill.intra.peff.net> (raw)
In-Reply-To: <CAJ-HmiZtHZ0qR9KdZ5mxzok18Ad6R8zLd3xwrvt+GQHu-qDrGQ@mail.gmail.com>
On Mon, Mar 19, 2018 at 04:14:31PM -0400, Nick Hunt wrote:
> oh, wait, switching branches didn't vaporize my changes, it auto-committed them.
> which is still weird and possibly a bug?
Are you sure that the changes were not already present on the
switched-to branch?
-Peff
prev parent reply other threads:[~2018-03-19 20:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-19 19:13 Potential git bug Nick Hunt
2018-03-19 20:14 ` Nick Hunt
2018-03-19 20:16 ` Jeff King [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=20180319201644.GA25618@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=nhunt11@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).