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

Re: [PATCH] clone: add remote.cloneDefault config option

From
Sean Barag <sean@barag.org>
Date
Aug 27, 2020, 14:00 UTC
Message-ID
<20200827140045.470411-1-sean@barag.org>
In-Reply-To
<xmqqpn7csoqd.fsf@gitster.c.googlers.com>
Show 10 quoted lines
> In order to realize any new feature that needs to read the existing
> (i.e. per-machine or per-user) configuration files to affect the
> behaviour of "git clone", whether it is the "give default to
> --origin option" or any other thing, first needs to fix the start-up
> sequence so that the configuration is read once before we process
> command line options, which is the norm.  Only after that is done,
> we can build the clone.defaultRemoteName and other features that
> would be affected by the settings of clone.* variables on top, and
> it is not wise to mix the foundation with a new feature that uses
> the foundation.

Makes sense! Thanks for all your help -- I _really_ appreciate it. I'll give it a try over the next few days.

Previous: Junio C Hamano
Message 7 of 7 in “clone: add remote.cloneDefault config option”
  1. clone: add remote.cloneDefault config optionSean Barag via GitGitGadget, Aug 26, 2020
  2. Junio C HamanoAug 26, 2020
  3. Derrick StoleeAug 26, 2020
  4. Junio C HamanoAug 26, 2020
  5. Sean BaragAug 27, 2020
  6. Junio C HamanoAug 27, 2020
  7. Sean BaragAug 27, 2020

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.