有时当我使用GitK时,我不关心分支上的一些提交,他们倾向于阻止我正在做的事情。
能够指定我想要的分支会很好,或者指定我想要排除的分支。
这可能吗?
Sometimes when I use GitK there's a load of commits on branches I'm not concerned with and they tend get in the way of what I'm doing.
It would be nice to be able to specify which branches I want, or specify which branches I want to exclude.
Is this possible?
最满意答案
你可以通过指定它作为gitk命令的参数来指定你想要的分支。 我假设你已经在使用 - 所有的,但你可能有兴趣知道,也有一个--not标志...虽然它有一些副作用,并且在大多数情况下不是很有用。
考虑一下如下所示的存储库:
git checkout feature-B gitk --all如果你没有指定参数,你只能得到你所在的分支:
gitk如果你指定多个分支,你会得到那些分支和完全合并的分支(即它们不会“伸出”)。 例如,在这里,我有feature-B , feature-C ,以及完全合并的feature-A和master ,但没有feature-D :
gitk feature-B feature-C最后,您可以使用--not标志忽略分支。 但是 ,由于分支引用了所有提交给它的提交,所以--not标志将忽略您指定的分支上的提交。
gitk feature-B --not feature-D gitk --all --not feature-D feature-C这两个都会给你:
在这里,提交Initial commit和1被忽略,因为它们属于分支feature-D 。 由于同样的原因,提交2也被忽略,但是显示为空提交,因为将提交3显示为分支中的初始提交是错误和误导的。 有时候这个标志会有帮助,但我通常不会使用它。
You can specify which branches you want by specifying them as arguments to the gitk command. I'm assuming that you're already using --all, but you might be interested to know that there's also a --not flag...although it has some side effects and is not too useful in most circumstances.
Consider a repository that looks like this:
git checkout feature-B gitk --allIf you specify no arguments, you get just the branch you're on:
gitkIf you specify multiple branches, you get those branches, and the branches that are fully merged (i.e. they don't "stick out"). For example, here I have feature-B, feature-C, along with the fully merged feature-A and master, but no feature-D:
gitk feature-B feature-CFinally, you can use the --not flag to ignore a branch. However, since a branch refers to all the commits that lead up to it, the --not flag will ignore commits that are on the branches that you do specify.
gitk feature-B --not feature-D gitk --all --not feature-D feature-CBoth of these will give you:
Here, the commits Initial commit and 1 are ignored, because they belonged to branch feature-D. Commit 2 is also ignored for the same reason, but is shown as an empty commit, since it would be incorrect and misleading to show commit 3 as the initial commit in the branch. This flag can be helpful sometimes, but I don't usually find myself using it.
更多推荐
发布评论