| commit | 7d5266a704ea55b11799bf0431d1648282f53d54 | |
| author | Shawn O. Pearce <spearce@spearce.org> | |
| Sun, 22 Jul 2007 08:49:06 +0000 (22 04:49 -0400) | ||
| committer | Shawn O. Pearce <spearce@spearce.org> | |
| Mon, 23 Jul 2007 05:28:35 +0000 (23 01:28 -0400) | ||
| tree | 0e7ce063c99e45d3b48fdf8bea261e25c0854939 | treesnapshot (tar.gz zip) |
| parent | a8139888f8d250c6d173ddbe892e98fc49763702 | commitdiff |
git-gui: Avoid unnecessary symbolic-ref call during checkout
If we are checking out the branch we are already on then there is no
need to call symbolic-ref to update the HEAD pointer to the "new"
branch name, it is already correct.
Currently this situation does not happen very often, but it can be
seen in some workflows where the user always recreates their local
branch from a remote tracking branch and more-or-less ignores what
branch he/she is on right now. As they say, ignorance is bliss.
This case will however become a tad more common when we overload
checkout_op to actually also perform all of our merges. In that
case we will likely see that the branch we want to "checkout" is
the current branch, as we are actually just merging into it.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
If we are checking out the branch we are already on then there is no
need to call symbolic-ref to update the HEAD pointer to the "new"
branch name, it is already correct.
Currently this situation does not happen very often, but it can be
seen in some workflows where the user always recreates their local
branch from a remote tracking branch and more-or-less ignores what
branch he/she is on right now. As they say, ignorance is bliss.
This case will however become a tad more common when we overload
checkout_op to actually also perform all of our merges. In that
case we will likely see that the branch we want to "checkout" is
the current branch, as we are actually just merging into it.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
| lib/checkout_op.tcl | diffblobblamehistory |