How can I view the Git history in Visual Studio Code?
来源： https://stackoverflow.com/questions/37899765/how-can-i-view-the-git-history-in-visual-studio-code
git-history-graph
visual studio code built-in story for reviewing git commit history and doing diffs of its contents
问题 In this SO question details are provided on use of out of box vscode "Timeline view" experience is covered as a way to look at commit history and diffs from a file scope perspective. Does out of box vscode support exist for gui review of a commit history, i.e. git log , and then diff'ng the contents of it, i.e. git show <commit id> , from a commit scope not Timeline file by file scope or extension marketplace offering such as GitLens, Git History or Git Graph? 来源： https://stackoverflow.com
visual studio code built-in story for reviewing git commit history and doing diffs of its contents
问题 In this SO question details are provided on use of out of box vscode "Timeline view" experience is covered as a way to look at commit history and diffs from a file scope perspective. Does out of box vscode support exist for gui review of a commit history, i.e. git log , and then diff'ng the contents of it, i.e. git show <commit id> , from a commit scope not Timeline file by file scope or extension marketplace offering such as GitLens, Git History or Git Graph? 来源： https://stackoverflow.com
Change the root commit parent to point to another commit (connecting two independent git repositories)
问题 I have a project that has more than 3 years of history in the svn repository. It was migrated to git, but the guy who did this, just take the last version and throw out all these 3 years of history. Now the project has the last 3-4 months of history in one repository, and I've imported the other 3 years of svn history into a new git repository. Is there some way to connect the root commit of the second repository into the last commit of the first one? It is something like this: * 2017-04-21 -
Change the root commit parent to point to another commit (connecting two independent git repositories)
问题 I have a project that has more than 3 years of history in the svn repository. It was migrated to git, but the guy who did this, just take the last version and throw out all these 3 years of history. Now the project has the last 3-4 months of history in one repository, and I've imported the other 3 years of svn history into a new git repository. Is there some way to connect the root commit of the second repository into the last commit of the first one? It is something like this: * 2017-04-21 -
How do I see a commit's path through git history, or “how it got in the current branch”?
问题 I'm looking in the commit history using gitk and git log and I'm trying to see how a specific commit arrived in a certain branch. I can see the commits in the history, so I know they are there. What I want to understand is how they got merged (they were supposed to remain on their own branch). This is a very large project and there are hundreds of commits between the commit in question and the current state of the branch, so I cannot clearly decipher through the limited DAG in gitk , and the
How do I see a commit's path through git history, or “how it got in the current branch”?
问题 I'm looking in the commit history using gitk and git log and I'm trying to see how a specific commit arrived in a certain branch. I can see the commits in the history, so I know they are there. What I want to understand is how they got merged (they were supposed to remain on their own branch). This is a very large project and there are hundreds of commits between the commit in question and the current state of the branch, so I cannot clearly decipher through the limited DAG in gitk , and the
How do I see a commit's path through git history, or “how it got in the current branch”?
I'm looking in the commit history using gitk and git log and I'm trying to see how a specific commit arrived in a certain branch. I can see the commits in the history, so I know they are there. What I want to understand is how they got merged (they were supposed to remain on their own branch). This is a very large project and there are hundreds of commits between the commit in question and the current state of the branch, so I cannot clearly decipher through the limited DAG in gitk , and the commit gets masked in other branches and merges and commit messages. To do this, I have been trying:
How can I tell if one commit is an ancestor of another commit (or vice-versa)?
Git is a DAG of snapshots, with each node on the graph representing a commit. Each commit can have 'n' parent commits. Given any two commits, is there a single, concise way to discern the "order" of these two in the DAG. git rev-list seems to be the most promising, but I can't seem to find the right incantation. Ideally, I'd have something like the following $ git related hash1 hash2 hash1 is ancestor of hash2 OR hash2 is ancestor of hash1 OR hash1 unrelated to hash2 OR hash1 is equal to hash2 Use git merge-base --is-ancestor <commit1> <commit2> There is more than one way to find the answer to
How can I tell if one commit is an ancestor of another commit (or vice-versa)?
问题 Git is a DAG of snapshots, with each node on the graph representing a commit. Each commit can have \'n\' parent commits. Given any two commits, is there a single, concise way to discern the \"order\" of these two in the DAG. git rev-list seems to be the most promising, but I can\'t seem to find the right incantation. Ideally, I\'d have something like the following $ git related hash1 hash2 hash1 is ancestor of hash2 OR hash2 is ancestor of hash1 OR hash1 unrelated to hash2 OR hash1 is equal