From: David Turner <dturner@twopensource.com>
To: git mailing list <git@vger.kernel.org>
Subject: Git autocorrect bug
Date: Wed, 04 Jun 2014 23:49:05 -0400 [thread overview]
Message-ID: <1401940145.18134.170.camel@stross> (raw)
$ cd [some existing git repo]
$ git git foo
WARNING: You called a Git command named 'git', which does not exist.
Continuing under the assumption that you meant 'init'
in 0.1 seconds automatically...
fatal: internal error: work tree has already been set
Current worktree: /home/dturner/git
New worktree: /home/dturner/git/foo
(I am extremely unlikely to fix this bug myself, since it only arises in
very rare circumstances).
next reply other threads:[~2014-06-05 3:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-05 3:49 David Turner [this message]
2014-06-05 6:06 ` Git autocorrect bug Øystein Walle
2014-06-05 6:10 ` Øystein Walle
2014-06-05 6:29 ` Duy Nguyen
2014-06-05 8:28 ` David Turner
2014-06-06 11:09 ` Duy Nguyen
2014-06-08 9:37 ` [PATCH] Fix "t0001: test git init when run via an alias" Nguyễn Thái Ngọc Duy
2014-06-10 18:48 ` Junio C Hamano
2014-06-11 10:57 ` Duy Nguyen
2014-06-12 17:11 ` Junio C Hamano
2014-06-10 18:53 ` Junio C Hamano
2014-06-10 19:09 ` 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=1401940145.18134.170.camel@stross \
--to=dturner@twopensource.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).