git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH] builtin-apply: Show a more descriptive error on failure when opening a patch

From
ABAlberto Bertogli <albertito@gmail.com>
Date
Apr 14, 2008, 15:30 UTC
Message-ID
<1208187027-29198-1-git-send-email-albertito@gmail.com>
In-Reply-To
<alpine.DEB.1.00.0804141532390.28504@racer>

When a patch can't be opened (it doesn't exist, there are permission problems, etc.) we get the usage text, which is not a proper indication of failure.

This patch fixes that by calling error() instead.
Signed-off-by: Alberto Bertogli <albertito@gmail.com>
---
On Mon, Apr 14, 2008 at 03:33:54PM +0100, Johannes Schindelin wrote:
Show 11 quoted lines
> On Mon, 14 Apr 2008, Alberto Bertogli wrote:
> 
> > +           if (fd < 0) {
> > +                   error("can't open patch '%s': %s", arg,
> > +                                   strerror(errno));
> > +                   return 1;
> > +           }
> 
> Do you absolutely want to retain the curly braces, and have two 
> statements?   I would prefer "return error(...)", and if you absolutely 
> insist on a return 1: "return !!error(...)".

No, I'm not insisting on any version, I just thought returning 1 would be better since it will become the script exit status; Now that I think a bit more about it, maybe I should just use die() instead.

Anyway, here's the version returning directly from error(); if you prefer it some other way just let me know.

Thanks,
		Alberto
 builtin-apply.c |    4 +++-
 1 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/builtin-apply.c b/builtin-apply.c
index abe73a0..56032ce 100644
--- a/builtin-apply.c
+++ b/builtin-apply.c
@@ -3121,7 +3121,9 @@ int cmd_apply(int argc, const char **argv, const char *unused_prefix)
 
 		fd = open(arg, O_RDONLY);
 		if (fd < 0)
-			usage(apply_usage);
+			return error("can't open patch '%s': %s", arg,
+					strerror(errno));
+
 		read_stdin = 0;
 		set_default_whitespace_mode(whitespace_option);
 		errs |= apply_patch(fd, arg, inaccurate_eof);
-- 
1.5.5.105.g7849.dirty
Previous: Johannes SchindelinNext: Junio C Hamano
Message 5 of 7 in “builtin-apply: Show a more descriptive error on failure when opening a patch”
  1. builtin-apply: Show a more descriptive error on failure when opening a patchAlberto Bertogli, Apr 13, 2008
  2. Junio C HamanoApr 13, 2008
  3. builtin-apply: Show a more descriptive error on failure when opening a patchAlberto Bertogli, Apr 14, 2008
  4. Johannes SchindelinApr 14, 2008
  5. builtin-apply: Show a more descriptive error on failure when opening a patchAlberto Bertogli, Apr 14, 2008
  6. Junio C HamanoApr 16, 2008
  7. Johannes SchindelinApr 14, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.