Use git log to view the commit history. Each commit has an associated revision specifier that is a hash key (e.g. 14b8d0982044b0c49f7a855e396206ee65c0e787 and b410ad4619d296f9d37f0db3d0ff5b9066838b39). To view the difference between two different commits, use git diff with the first few characters of the revision specifiers of both commits, like so: # diff between commits 14b8… and … Read more
No, there is no ClearCase to Git bridge, convertor or adaptor that I know of (retaining the full history, with all its events). It is best to: restrict a git repo to an UCM component (while a Vob can contain multiple component and be way too big for a Git repo to handle) add in … Read more
There is a guide to splitting commits in the rebase manpage. The quick summary is: Perform an interactive rebase including the target commit (e.g. git rebase -i <commit-to-split>^ branch) and mark it to be edited. When the rebase reaches that commit, use git reset HEAD^ to reset to before the commit, but keep your work … Read more
Branches are just pointers to commits in git. In git each commit has a complete source tree, it is a very different structure from svn where all branches and tags (by convention) live in separate ‘folders’ of the repository alongside the special ‘trunk’. If the branch was merged into another branch before it was deleted … Read more
How can you get the tree-like view of commits in terminal? git log –graph –oneline –all is a good start. You may get some strange letters. They are ASCII codes for colors and structure. To solve this problem add the following to your .bashrc: export LESS=”-R” such that you do not need use Tig’s ASCII … Read more
Before executing this command keep in mind that it will leave you in detached head status Use git checkout <sha1> to check out a particular commit. Where <sha1> is the commit unique number that you can obtain with git log Here are some options after you are in detached head status: Copy the files or … Read more
With modern Git (1.8.3.4 in my case) and not using branches you can do: $ git rev-list –count HEAD 68 But this has all kinds of issues and might not be easy to reproduce or easy to get back to the commit hash in case you need to. So try to avoid it or use … Read more
Detailed Solution See the note at the end of this answer (last paragraph) for a quick alternative to git submodules using npm 😉 In the following answer, you will know how to extract a folder from a repository and make a git repository from it and then including it as a submodule instead of a … Read more