Confusing --graph --all output with detached branches

If you end up with a history containing commit A with parent B, where a detached branch is merged into A while an unrelated branch branches off of B, you will get the following output: $ git log --graph --all * commit ff4265fcbfe94a2abe93c97d86e0d9f0e0a136cb |\ Merge: 8b62de9 0bbc311 | |

Minor bug with help.autocorrect.

If you mis-type a git command starting with a non-letter, git internals will spit out some errors at you. $ git 5fetch error: invalid key: pager.5fetch error: invalid key: alias.5fetch git: '5fetch' is not a git command. See 'git --help'. Did you mean this? fetch $ git \#fetch error:

workdirs: cannot clone a local workdir directory

I reported this before, but now I have a nice topic to hang it on - I have re-reproduced the bug using a build from master as of today, using the new worktree commands. Reproduction: Creating a repo `foo`, checkout --to'ing it to ../bar, then try to clone both resulting repositories.. $ git

Linked workdirs break typo-correction.

: Bjørnar Snoksrud bsnok...@cisco.com Date: Thu Jun 25 16:08:01 2015 +0200 folder diff --git a/folder/file b/folder/file new file mode 100644 index 000..e69de29 bsnoksru@calculon ~/git/bar/folder (master) $ git branch foo bsnoksru@calculon ~/git/bar/folder (master) $ git checkout foo

Cannot clone a linked working directory.

Summary: When creating a linked working directory with `git checkout --to`, you cannot clone from the local path. This works when cloning the main repository directory. I couldn't find anything the the documentation for `git checkout` that indicates that this shouldn't work. Repro: Creating a