| commit | 258871d3058a3117d204009b7173bf8c7df2414d | |
| author | Shawn O. Pearce <spearce@spearce.org> | |
| Fri, 9 Feb 2007 00:41:32 +0000 (8 19:41 -0500) | ||
| committer | Shawn O. Pearce <spearce@spearce.org> | |
| Fri, 9 Feb 2007 00:41:32 +0000 (8 19:41 -0500) | ||
| tree | aceafa63846e42cb7fd1f37a5006cf952c2e012d | treesnapshot (tar.gz zip) |
| parent | 2ebba528dcb64ec1a408ec3b06cf9f928a7fb76d | commitdiff |
git-gui: Select subcommands like git does.
If we are invoked as `git-foo`, then we should run the `foo` subcommand,
as the user has made some sort of link from `git-foo` to our actual
program code. So we should honor their request.
If we are invoked as `git-gui foo`, the user has not made a link (or
did, but is not using it right now) so we should execute the `foo`
subcommand.
We now can start the single commit UI mode via `git-citool` and also
through `git gui citool`.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
If we are invoked as `git-foo`, then we should run the `foo` subcommand,
as the user has made some sort of link from `git-foo` to our actual
program code. So we should honor their request.
If we are invoked as `git-gui foo`, the user has not made a link (or
did, but is not using it right now) so we should execute the `foo`
subcommand.
We now can start the single commit UI mode via `git-citool` and also
through `git gui citool`.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
| git-gui.sh | diffblobblamehistory |