Thread (3 messages) flat view 3 messages, 2 authors, 2016-06-15

Re: Doesn't disambiguate between 'external command failed' and 'command not found'

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:51:33

Possibly related (same subject, not in this thread)

Jeff King [off-list ref] writes:
On Wed, Jul 06, 2011 at 01:58:03PM -0400, Jeff King wrote:
quoted
quoted
Like this? I've replaced "Check the #!-line of the git-%s script." with
"Maybe git-%s is broken?" to be less technical and specific..
Yeah, looks good to me (unless somebody wants to do something more
elaborate to catch other exec problems, but I personally don't think
it's worth the effort).
One minor nit, though. I haven't been paying attention to the progress
of the gettext topics, but should this message:
quoted
+static const char bad_interpreter_advice[] =
+	"'%s' appears to be a git command, but we were not\n"
+	"able to execute it. Maybe git-%s is broken?";
Actually be inside _() for gettext?
I would mark it with N_() and then the calling site inside die() with _()
if I were doing this.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help