author | Shawn O. Pearce <spearce@spearce.org> | |
Mon, 8 Oct 2007 05:23:54 +0000 (22:23 -0700) | ||
committer | Shawn O. Pearce <spearce@spearce.org> | |
Wed, 10 Oct 2007 05:12:17 +0000 (01:12 -0400) | ||
commit | 6bdf5e5f20c792ad0c5d5ba941d7e637aca86d32 | |
tree | 31afd464266edb04697bfa21b8a9a454abfb8136 | tree | snapshot |
parent | 1cad232f92794834c8e70dfc0a1f35431d2c05cd | commit | diff |
git-gui: Consolidate the Fetch and Push menus into a Remote menu
Sometimes the Fetch menu looks really odd, such as if you are in a
repository that has no remotes configured when you start git-gui.
Here we didn't have any items to add to the Fetch menu so it was a
tad confusing for the end-user to see an empty menu on the menu bar.
We now place all of the commands related to fetching and pushing of
changes into a single "Remote" menu. This way we have a better class
of bucket that we can drop additional remote related items into such
as doing a remote merge or editing the remote configuration specs.
The shortcuts to execute fetch/remote prune/push on existing remote
specifications are now actually submenus listing the remotes by name.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
Sometimes the Fetch menu looks really odd, such as if you are in a
repository that has no remotes configured when you start git-gui.
Here we didn't have any items to add to the Fetch menu so it was a
tad confusing for the end-user to see an empty menu on the menu bar.
We now place all of the commands related to fetching and pushing of
changes into a single "Remote" menu. This way we have a better class
of bucket that we can drop additional remote related items into such
as doing a remote merge or editing the remote configuration specs.
The shortcuts to execute fetch/remote prune/push on existing remote
specifications are now actually submenus listing the remotes by name.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
git-gui.sh | diff | blob | history | |
lib/remote.tcl | diff | blob | history |