[PATCH v2 0/5] provide better error messages for @{upstream} - Zbigniew Jędrzejewski-Szmek

From: "Zbigniew Jędrzejewski-Szmek" <zbyszek@in.waw.pl>
To: git@vger.kernel.org, gitster@pobox.com
Cc: peff@peff.net, Matthieu.Moy@grenoble-inp.fr,
	"Zbigniew Jędrzejewski-Szmek" <zbyszek@in.waw.pl>
Subject: [PATCH v2 0/5] provide better error messages for @{upstream}
Date: Sat, 14 Apr 2012 09:54:30 +0200	[thread overview]
Message-ID: <1334390075-25467-1-git-send-email-zbyszek@in.waw.pl> (raw)
In-Reply-To: <20120412204055.GA21018@sigill.intra.peff.net>

Hi,

v2:

- Better commit descriptions (hopefully)
- error_message used in tests in one more place
- Error message changed from
  "Upstream branch '%s' not fetched from remote '%s'"
  to
  "Upstream branch '%s' not stored as a remote-tracking branch".

[I thought about using
 "No tracking brach for remote branch '%s'"
 or
 "No remote-tracking branch for upstream branch '%s'"
 or
 "Tracking branch not configured for upstream branch '%s'"
 but neither one is convincing. ]

Zbigniew Jędrzejewski-Szmek (5):
      t1507: add tests to document @{upstream} behaviour
      Provide branch name in error message when using @{u}
      Provide better message for barnhc_wiht_tpyo@{u}
      Be more specific if upstream branch is not tracked
      i18n: mark @{upstream} error messages for translation

 sha1_name.c                   |   20 ++++++++--
 t/t1507-rev-parse-upstream.sh |   81 +++++++++++++++++++++++++++++++++++++++--
 2 files changed, 94 insertions(+), 7 deletions(-)

-- 
1.7.10.344.g387ed