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

Re: [PATCH v2 0/2] Improve git-pull's option parsing

From
Junio C Hamano <gitster@pobox.com>
Date
Jun 2, 2015, 20:26 UTC
Message-ID
<xmqqpp5d26wz.fsf@gitster.dls.corp.google.com>
In-Reply-To
<1433254973-13797-1-git-send-email-pyokagan@gmail.com>
Paul Tan <pyokagan@gmail.com> writes:
> However, certain functions in git-pull assume that the positional
> parameters do not contain any options. Fix this by making git-pull
> handle git-fetch's options as well at the option parsing stage.
Good.
Previous: Paul Tan
Message 4 of 4 in “Improve git-pull's option parsing”
  1. 0/2 Improve git-pull's option parsingPaul Tan, Jun 2, 2015
  2. 1/2 pull: handle git-fetch's options as wellPaul Tan, Jun 2, 2015
  3. 2/2 pull: use git-rev-parse --parseopt for option parsingPaul Tan, Jun 2, 2015
  4. Junio C HamanoJun 2, 2015

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.