With git 2.8 (Q12016), you will be able to initiate the fetch of submodules… in parallel! See commit fbf7164 (16 Dec 2015) by Jonathan Nieder (artagnon). See commit 62104ba, commit fe85ee6, commit c553c72, commit bfb6b53, commit b4e04fb, commit 1079c4b (16 Dec 2015) by Stefan Beller (stefanbeller). (Merged by Junio C Hamano — gitster — in … Read more
Git is confused, because 12382 looks like a commit hash. Use the fully qualified name to checkout the branch: git checkout refs/heads/12382 — or, if it’s a remote branch: git checkout refs/remotes/origin/12382 —
These are three different commands: Git pull is a git fetch followed by git merge – read here Git fetch fetches info about remote repositories – read here Git sync does everything in one command meaning pull and push read here If you want to compare git and svn workflow then git pull is like … Read more
I found this comment by Arcanis (the lead maintainer of Yarn) on an issue asking about what to include in a .gitignore. It may answer your question: .yarn/plugins and .yarn/releases contain the Yarn releases used in the current repository (as defined by yarn set version). You will want to keep them versioned (this prevents potential … Read more
Use the –word-diff option for git diff For example, git diff –word-diff=color: and git diff –word-diff=plain: There’s also –word-diff-regex=<regex> See git help diff for more info.
Vi is giving you a hint about “properly” formatting your commit message. While there is no specific enforcement of one message style w.r.t. another, “traditionally” Git commit messages are structured this way: A short title describing the changeset (usually less than 50-60 characters); One blank line; A more complete description of the commit, optionally divided … Read more
Git branches do not have “heads” in the Mercurial sense. There is only one thing called HEAD, and it’s effectively a symlink to the commit you currently have checked out. In the case of hosted repositories like GitHub, there is no commit checked out—there’s just the repository history itself. (Called a “bare” repo.) The reason … Read more
Actualy, there’s a really cool command I learned recently that will do exactly what you want: git commit-tree -p HEAD^2 -p HEAD^1 -m “Commit message” “HEAD^{tree}” This will create a new commit based on what is currently HEAD, but pretend that it’s parents were HEAD^2,HEAD^1 (note this is the reversed order). git-commit-tree prints the new … Read more
What went wrong Where you went wrong is doing the $ git add . That adds everything, so also foo/bar, to the index of the current repository (ready to be committed thus). Correct way If you just don’t do that and continue with $ git submodule add https://github.com/CarloWood/XYZ.git foo/bar then that should work; this would … Read more
Either one or more files are being modified during your operation, or something is causing inconsistent reads (e.g. failing hardware). Short version: Git’s developers did not intend for it to be used on volatile files. Due to the layout* that Git uses for “loose objects” and the limited filesystem semantics that it assumes**, Git must … Read more