summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: 37f1db8)
raw | patch | inline | side by side (parent: 37f1db8)
author | Shawn O. Pearce <spearce@spearce.org> | |
Thu, 8 Feb 2007 20:59:39 +0000 (15:59 -0500) | ||
committer | Shawn O. Pearce <spearce@spearce.org> | |
Thu, 8 Feb 2007 20:59:39 +0000 (15:59 -0500) |
If the user has created (or deleted) a branch through an external tool,
and uses Rescan, they probably are trying to make git-gui update to show
their newly created branch.
So now we load all known heads and update the branch menu during any
rescan operation, just in-case the set of known branches was modified.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
and uses Rescan, they probably are trying to make git-gui update to show
their newly created branch.
So now we load all known heads and update the branch menu during any
rescan operation, just in-case the set of known branches was modified.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
git-gui.sh | patch | blob | history |
diff --git a/git-gui.sh b/git-gui.sh
index ef353319ec78116f4c1342354de8e5b4af77e498..4116821d8d41d3b357f0acbdcef4a51b94def76b 100755 (executable)
--- a/git-gui.sh
+++ b/git-gui.sh
global HEAD PARENT MERGE_HEAD commit_type
global ui_index ui_workdir ui_status_value ui_comm
global rescan_active file_states
- global repo_config
+ global repo_config single_commit
if {$rescan_active > 0 || ![lock_index read]} return
$ui_comm edit modified false
}
+ if {!$single_commit} {
+ load_all_heads
+ populate_branch_menu
+ }
+
if {$honor_trustmtime && $repo_config(gui.trustmtime) eq {true}} {
rescan_stage2 {} $after
} else {