diff options
| author | Shawn O. Pearce <spearce@spearce.org> | 2007-07-25 04:54:53 -0400 |
|---|---|---|
| committer | Shawn O. Pearce <spearce@spearce.org> | 2007-07-25 04:54:53 -0400 |
| commit | ead49f5a4f6c87e5dc61ed5daaeda1bae7644d05 (patch) | |
| tree | 3571d82bdc70210d83a2b5176715f6639156d8ad /git-gui/lib/diff.tcl | |
| parent | git-gui: Cleanup bindings within merge dialog (diff) | |
| download | git-ead49f5a4f6c87e5dc61ed5daaeda1bae7644d05.tar.gz git-ead49f5a4f6c87e5dc61ed5daaeda1bae7644d05.zip | |
git-gui: Format tracking branch merges as though they were pulls
If we are merging a tracking branch we know exactly what remote URL
that branch is fetched from, and what its name is on that remote
repository. In this case we can setup a merge message that looks
just like a standard `git-pull $remote $branch` operation by filling
out FETCH_HEAD before we start git-merge, and then run git-merge just
like git-pull does.
I think the result of this behavior is that merges look a lot nicer
when the came off of local tracking branches, because they no longer
say "commit 'origin/...'" to describe the commit being merged but
instead now mention the specific repository we fetched those commits
from.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
Diffstat (limited to 'git-gui/lib/diff.tcl')
0 files changed, 0 insertions, 0 deletions
