This series is on top of next. git remote update <non-existing> would previously silently do nothing. With this patch series, it will (with 1/3) error out when non-existing groups are given, and with 2/3 & 3/3 it will use a remote if a group cannot be found. This enables "git remote update origin" for example. All previous uses of "git remote update <x>" that did something useful should still work exactly as before. There seems to be no current way to check for the existence of a configured remote, so 2/3 adds a remote_is_configured() function which checks for a configured remote. Finn Arne Gangstad (3): git remote update: Report error for non-existing groups remote: New function remote_is_configured() git remote update: Fallback to remote if group does not exist Documentation/git-remote.txt | 2 +- builtin-remote.c | 17 ++++++++++++++--- remote.c | 11 +++++++++++ remote.h | 1 + 4 files changed, 27 insertions(+), 4 deletions(-) -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html