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

Re: [PATCH v6 0/6] Move PGP verification out of verify-tag

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 18, 2016, 20:15 UTC
Message-ID
<xmqqshyi4qsj.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<1460932021-27633-1-git-send-email-santiago@nyu.edu>
santiago@nyu.edu writes:
>    I'm unsure about the 80-column
>    on 4/6, the ternary operator is rather long.
You can do something like this:
        type = sha1_object_info(sha1, NULL);
        if (type != OBJ_TAG)
                return error("%s: cannot verify a non-tag object of type %s.",
                             report_name ?
                             report_name :
                             find_unique_abbrev(sha1, DEFAULT_ABBREV),
                             typename(type));
        buf = read_sha1_file(sha1, &type, &size);
        if (!buf)
                return error("%s: unable to read file.",
                             report_name ?
                             report_name :
                             find_unique_abbrev(sha1, DEFAULT_ABBREV));
Thanks.
Previous: Eric SunshineNext: Jeff King
Message 14 of 15 in “Move PGP verification out of verify-tag”
  1. 0/6 Move PGP verification out of verify-tagsantiago@nyu.edu, Apr 17, 2016
  2. 1/6 builtin/verify-tag.c: ignore SIGPIPE in gpg-interfacesantiago@nyu.edu, Apr 17, 2016
  3. 2/6 t7030: test verifying multiple tagssantiago@nyu.edu, Apr 17, 2016
  4. 3/6 verify-tag: change variable name for readabilitysantiago@nyu.edu, Apr 17, 2016
  5. Eric SunshineApr 18, 2016
  6. Jeff KingApr 19, 2016
  7. 4/6 verify-tag: add sha1 argument to verify_tag()santiago@nyu.edu, Apr 17, 2016
  8. Eric SunshineApr 18, 2016
  9. Junio C HamanoApr 18, 2016
  10. 5/6 verify-tag: move verification code to tag.csantiago@nyu.edu, Apr 17, 2016
  11. 6/6 tag -v: verfy directly rather than exec-ing verify-tagsantiago@nyu.edu, Apr 17, 2016
  12. Eric SunshineApr 18, 2016
  13. Eric SunshineApr 18, 2016
  14. Junio C HamanoApr 18, 2016
  15. Jeff KingApr 19, 2016

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.