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

Re: [PATCH 2/2] [GSOC] interpret-trailer: easy parse trailer value

From
ZheNing Hu <adlternative@gmail.com>
Date
Mar 21, 2021, 03:29 UTC
Message-ID
<CAOLTT8Q7yNscYrYHWJQcsGn67MjWe15nd7SnCEd5QVUG0A6dRg@mail.gmail.com>
In-Reply-To
<xmqqft0pk018.fsf@gitster.g>
Junio C Hamano <gitster@pobox.com> 于2021年3月21日周日 上午5:06写道:
Show 19 quoted lines
>
> "ZheNing Hu via GitGitGadget" <gitgitgadget@gmail.com> writes:
>
> > diff --git a/commit.h b/commit.h
> > index 49c0f503964e..970a73ccd5be 100644
> > --- a/commit.h
> > +++ b/commit.h
> > @@ -371,4 +371,6 @@ int parse_buffer_signed_by_header(const char *buffer,
> >                                 struct strbuf *signature,
> >                                 const struct git_hash_algo *algop);
> >
> > +const char *find_author_by_nickname(const char *name);
> > +
> >  #endif /* COMMIT_H */
>
> As I already said, we do not want to pretend that this is a
> generally reusable helper function.  We should at least have a
> comment to tell people to never add new callers to this function,
> with explanation of the reason.
Do you think this is appropriate?
@@ -370,5 +370,15 @@ int parse_buffer_signed_by_header(const char *buffer,
                                  struct strbuf *payload,
                                  struct strbuf *signature,
                                  const struct git_hash_algo *algop);
+/*
+ * Calling `find_author_by_nickname` to find the "author <email>" pair
+ * in the most recent commit which matches "--author=name".
+ *
+ * Note that `find_author_by_nickname` is not reusable, because it haven't
+ * reset flags for parsed objects. The only safe way to use
`find_author_by_nickname`
+ * (without rewriting the revision traversal machinery) is to spawn a
+ * subprocess and do find_author_by_nickname() in it.
+ */
+const char *find_author_by_nickname(const char *name);

Thanks.
Previous: Junio C HamanoNext: Junio C Hamano
Message 5 of 23 in “[GSOC] interpret-trailer: easy parse trailer value”
  1. 0/2 [GSOC] interpret-trailer: easy parse trailer valueZheNing Hu via GitGitGadget, Mar 20, 2021
  2. 1/2 [GSOC] commit: add --trailer optionZheNing Hu via GitGitGadget, Mar 20, 2021
  3. 2/2 [GSOC] interpret-trailer: easy parse trailer valueZheNing Hu via GitGitGadget, Mar 20, 2021
  4. Junio C HamanoMar 20, 2021
  5. ZheNing HuMar 21, 2021
  6. Junio C HamanoMar 21, 2021
  7. ZheNing HuMar 21, 2021
  8. 0/2 [GSOC] interpret-trailer: easy parse trailer valueZheNing Hu via GitGitGadget, Mar 21, 2021
  9. 2/2 [GSOC] interpret-trailer: easy parse trailer valueZheNing Hu via GitGitGadget, Mar 21, 2021
  10. Bagas SanjayaMar 21, 2021
  11. ZheNing HuMar 21, 2021
  12. Junio C HamanoMar 21, 2021
  13. Bagas SanjayaMar 22, 2021
  14. Junio C HamanoMar 22, 2021
  15. Christian CouderMar 21, 2021
  16. ZheNing HuMar 21, 2021
  17. Junio C HamanoMar 21, 2021
  18. ZheNing HuMar 22, 2021
  19. Christian CouderMar 22, 2021
  20. ZheNing HuMar 22, 2021
  21. Junio C HamanoMar 22, 2021
  22. ZheNing HuMar 23, 2021
  23. 1/2 [GSOC] commit: add --trailer optionZheNing Hu via GitGitGadget, Mar 21, 2021

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.