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

Re: [PATCH 1/1] [Outreachy] merge-ours: include parse-options

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Oct 30, 2019, 21:58 UTC
Message-ID
<nycvar.QRO.7.76.6.1910302257480.46@tvgsbejvaqbjf.bet>
In-Reply-To
<xmqqk18n3s3i.fsf@gitster-ct.c.googlers.com>
Hi Junio,
On Wed, 30 Oct 2019, Junio C Hamano wrote:
Show 9 quoted lines
> "george espinoza via GitGitGadget" <gitgitgadget@gmail.com> writes:
>
> > From: george espinoza <gespinoz2019@gmail.com>
> >
> > Teach this command which currently handles its own argv to use
> > parse-options instead because parse-options helps make sure we handle
> > user input like -h in a standardized way across the project.
>
> Sorry, but why do we even want to do this?

It _is_ a command you can run via `git merge-ours` by mistake. Don't you think it would be nice for users to at least get a synopsis?

Ciao, Dscho

Previous: George EspinozaNext: Junio C Hamano
Message 8 of 9 in “[Outreachy] merge-ours: include a parse-option”
  1. 0/1 [Outreachy] merge-ours: include a parse-optionGeorge Espinoza via GitGitGadget, Oct 28, 2019
  2. 1/1 [Outreachy] merge-ours: include parse-optionsgeorge espinoza via GitGitGadget, Oct 28, 2019
  3. Johannes SchindelinOct 29, 2019
  4. Emily ShafferOct 29, 2019
  5. George EspinozaOct 30, 2019
  6. Junio C HamanoOct 30, 2019
  7. George EspinozaOct 30, 2019
  8. Johannes SchindelinOct 30, 2019
  9. Junio C HamanoNov 2, 2019

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.