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

Re: [PATCH] rev-parse: clarify documentation for the --verify option

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 1, 2013, 16:56 UTC
Message-ID
<7vli92jijz.fsf@alter.siamese.dyndns.org>
In-Reply-To
<7vwqsnnpwj.fsf@alter.siamese.dyndns.org>
Junio C Hamano <gitster@pobox.com> writes:
> Because the primary use case of this option is to implement end-user
> input validation, I think it would be helpful to clarify use of the
> peeler here.  Perhaps
> ...

A "SQUASH???" patch on top of your original is queued on 'pu', together with the earlier "^{object}" peeler patch. Comments, improvements, etc. would be nice.

Thanks.
Previous: Junio C HamanoNext: Michael Haggerty
Message 3 of 6 in “rev-parse: clarify documentation for the --verify option”
  1. rev-parse: clarify documentation for the --verify optionMichael Haggerty, Mar 30, 2013
  2. Junio C HamanoMar 31, 2013
  3. Junio C HamanoApr 1, 2013
  4. Michael HaggertyApr 2, 2013
  5. Junio C HamanoApr 2, 2013
  6. Michael HaggertyApr 2, 2013

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.