summaryrefslogtreecommitdiff
path: root/git-parse-remote.sh
diff options
context:
space:
mode:
authorLibravatar Shawn O. Pearce <spearce@spearce.org>2007-05-02 14:25:22 -0400
committerLibravatar Shawn O. Pearce <spearce@spearce.org>2007-05-07 23:35:52 -0400
commit349f92e3a25216b6f79c58044d74b61c89de20b8 (patch)
tree74a18f7b83f63a16d8717272749a66d7fd0d0be5 /git-parse-remote.sh
parentgit-gui: Move merge support into a namespace (diff)
downloadtgif-349f92e3a25216b6f79c58044d74b61c89de20b8.tar.xz
git-gui: Show all possible branches for merge
Johannes Sixt pointed out that git-gui was randomly selecting which branch (or tag!) it will show in the merge dialog when more than one ref points at the same commit. This can be a problem for the user if they want to merge a branch, but the ref that git-gui selected to display was actually a tag that points at the commit at the tip of that branch. Since the user is looking for the branch, and not the tag, its confusing to not find it, and worse, merging the tag causes git-merge to generate a different message than if the branch was selected. While I am in here and am messing around I have changed the for-each-ref usage to take advantage of its --tcl formatting, and to fetch the subject line of the commit (or tag) we are looking at. This way we could present the subject line in the UI to the user, given them an even better chance to select the correct branch. Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
Diffstat (limited to 'git-parse-remote.sh')
0 files changed, 0 insertions, 0 deletions