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

[PATCH 0/1] [Outreachy] merge-ours: include a parse-option

From
GGGeorge Espinoza via GitGitGadget <gitgitgadget@gmail.com>
Date
Oct 28, 2019, 23:42 UTC
Message-ID
<pull.425.git.1572306149.gitgitgadget@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. Also deleted the NO_PARSEOPT flag from git.c to coincide with the conversion of the structure in this command since merge-ours now uses parse-options and needed to update git.c accordingly.

Outreachy Micro-Project #3 
Signed-off-by: george espinoza gespinoz2019@gmail.com
[gespinoz2019@gmail.com]
george espinoza (1):
  [Outreachy] merge-ours: include parse-options
 builtin/merge-ours.c | 14 ++++++++++----
 git.c                |  2 +-
 2 files changed, 11 insertions(+), 5 deletions(-)
base-commit: 566a1439f6f56c2171b8853ddbca0ad3f5098770
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-425%2FGeorgecanfly%2Fmerge-ours-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-425/Georgecanfly/merge-ours-v1
Pull-Request: https://github.com/gitgitgadget/git/pull/425
-- 
gitgitgadget
Next: george espinoza via GitGitGadget
Message 1 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.