From: Sam Vilain Date: Sat, 30 Jun 2007 08:56:17 GMT Subject: [PATCH] git-remote: allow 'git-remote fetch' as a synonym for 'git fetch' Message-ID: <11831937822249-git-send-email-sam.vilain@catalyst.net.nz> In-Reply-To: <1183193782172-git-send-email-sam.vilain@catalyst.net.nz> From: Sam Vilain I found myself typing this when doing remote-like things. Perhaps other people will find this useful Signed-off-by: Sam Vilain --- Documentation/git-remote.txt | 4 ++++ git-remote.perl | 4 ++++ 2 files changed, 8 insertions(+), 0 deletions(-) diff --git a/Documentation/git-remote.txt b/Documentation/git-remote.txt index 61a6022..b462ccd 100644 --- a/Documentation/git-remote.txt +++ b/Documentation/git-remote.txt @@ -64,6 +64,10 @@ With `-n` option, the remote heads are not confirmed first with `git ls-remote `; cached information is used instead. Use with caution. +'fetch':: + +Synonym for `git fetch `, and accepts all the same options. + 'update':: Fetch updates for a named set of remotes in the repository as defined by diff --git a/git-remote.perl b/git-remote.perl index b59cafd..2c60cae 100755 --- a/git-remote.perl +++ b/git-remote.perl @@ -404,11 +404,15 @@ elsif ($ARGV[0] eq 'add') { } add_remote($ARGV[1], $ARGV[2], \%opts); } +elsif ($ARGV[0] eq 'fetch') { + exec("git-fetch", @ARGV[1..$#ARGV]); +} else { print STDERR "Usage: git remote\n"; print STDERR " git remote add \n"; print STDERR " git remote show \n"; print STDERR " git remote prune \n"; print STDERR " git remote update [group]\n"; + print STDERR " git remote fetch ...\n"; exit(1); } -- 1.5.2.1.1131.g3b90