summaryrefslogtreecommitdiff
path: root/t/t4103-apply-binary.sh
diff options
context:
space:
mode:
authorLibravatar Shawn O. Pearce <spearce@spearce.org>2007-03-12 13:03:47 -0400
committerLibravatar Shawn O. Pearce <spearce@spearce.org>2007-03-12 13:03:47 -0400
commitc7bafad10d294cc0b26ab6171efd89dd9b132f70 (patch)
treefaad73b1772cc8632ceb02ad4fb41e4ca2a5227b /t/t4103-apply-binary.sh
parentgit-gui: Make 'make' quieter by default (diff)
downloadtgif-c7bafad10d294cc0b26ab6171efd89dd9b132f70.tar.xz
git-gui: Allow committing empty merges
Johannes Sixt noticed that git-gui would not let the user commit a merge created by `git merge -s ours` as the ours strategy does not alter the tree (that is HEAD^1^{tree} = HEAD^{tree} after the merge). The same issue arises from amending such a merge commit. We now permit an empty commit (no changed files) if we are doing a merge commit. Core Git does this with its command line based git-commit tool, so it makes sense for the GUI to do the same. Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
Diffstat (limited to 't/t4103-apply-binary.sh')
0 files changed, 0 insertions, 0 deletions