From: David Turner <novalis@novalis.org>
To: git@vger.kernel.org
Subject: Why does git checkout -b touch the index?
Date: Fri, 14 Oct 2016 10:35:56 -0400 [thread overview]
Message-ID: <1476455756.32360.2.camel@frank> (raw)
If I do "git checkout -b fleem", with no additional flags, why does it
need to rewrite the index? Or even read the index?
(this is kind of a bug report, I guess, but it's a pretty minor bug that
I only noticed because I was out of hard drive space)
next reply other threads:[~2016-10-14 14:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-14 14:35 David Turner [this message]
2016-10-14 16:07 ` Why does git checkout -b touch the index? 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1476455756.32360.2.camel@frank \
--to=novalis@novalis.org \
--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).