gitk

问题 When I'm loading gitk I get an error about an argument Error in startup script: bad argument "zoomed": must be normal, iconic, or withdrawn while executing "wm state . $geometry(state)" (procedure "makewindow" line 320) invoked from within "makewindow" (file "/usr/local/git/bin/gitk" line 11250) Anybody knows a solution? I'm working on Mac OS X 10.6.3 thx! 回答1: As mention in this blog post: 使用Macport安裝mercurial結果安裝了一堆相依的library，結果造成gitk不能執行 Err... I meant: The results using Macport

问题 So I have a file called one.txt that I have been modifying over the years on master branch. gitk one.txt will show the entire history of that one particular file. However after I changed one.txt => two.txt , gitk two.txt doesn't show any change before the rename. I tried gitk --follow two.txt , but only gave the comment for each commit, but not the actual file change information. I know I can do git log --follow two.txt , but you have to gitk each SHA1 value to each what is being changed. So

问题 Just gitk or gitk --all can try to fill up all memory on big repository. I know than I can gitk -n 1000 to limit it. Also I can killall git (or even Alt+SysRq+F if haven't stopped it in time) to stop it in middle of thrashing. Is there more proper way to make gitk don't load more commits and stop it's git subprocess without hacks or lengthy gitk restart? 回答1: You can also limit gitk by branchname. Instead of using gitk --all to see all branches, just use 'gitk branchname'. This might limit

问题 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

问题 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

问题 After much searching, I have not found a satisfactory method that is easy to use to view the complete history of a moved file in Git and more importantly in Gitk. Using git log --follow [filePath] and even gitk --follow [filePath] gives you the commits that the file was involved in but will not show you the actual change history of the file before the move. I have thus come up with a crude but simple workaround solution. Do a gitk on the file that has been moved: gitk [newFilePath] . Copy the

问题 After much searching, I have not found a satisfactory method that is easy to use to view the complete history of a moved file in Git and more importantly in Gitk. Using git log --follow [filePath] and even gitk --follow [filePath] gives you the commits that the file was involved in but will not show you the actual change history of the file before the move. I have thus come up with a crude but simple workaround solution. Do a gitk on the file that has been moved: gitk [newFilePath] . Copy the

问题 Currently for merges without conflicts gitk shows no diffs. Is it possible to have the diffs resulting from a merge (which are indeed there, e.g. git diff HEAD~1 after the merge shows these diffs) shown by defautl, e.g. using a command line switch? Or why does gitk by default not show them? 回答1: By default gitk does the same thing as the --cc option to git diff and compresses the merge to only show diff chunks that don't come directly from one or other parent. This is usually more helpful as

问题 I'm somewhat new to Git and what I'm trying to do seems like it should be possible. Basically I've been working off of clone of a repo and have made quite a few local commits. Is there a way to see the diff of the 'sum' of all my changes and the original repo version? I would assume this would be possible because Git will essentially do this when I do a push . Here is an example of what I'm trying to do: in gitk I will see something like this: * - [mybranch] Added '42' to end of answers.txt

问题 I am using the command line version of Git and gitk. I want to see the full version tree, not just the part that is reachable from the currently checked out version. Is it possible? 回答1: You can try the following: gitk --all You can tell gitk what to display using anything that git rev-list understands, so if you just want a few branches, you can do: gitk master origin/master origin/experiment ... or more exotic things like: gitk --simplify-by-decoration --all 回答2: if you happen to not have a