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

Re: [PATCH v2 0/7] remote rename/remove: improve handling of configuration values

From
Matt Rogers <mattr94@gmail.com>
Date
Jan 25, 2020, 00:39 UTC
Message-ID
<CAOjrSZtT0bX=hhH=OZdA80T_Thgn9drG66xcVMYjo7Q=5Cw_Bw@mail.gmail.com>
In-Reply-To
<xmqq36c4zi0x.fsf@gitster-ct.c.googlers.com>
Yeah, I just resubmitted so you should be good to go
On Fri, Jan 24, 2020 at 4:10 PM Junio C Hamano <gitster@pobox.com> wrote:
Show 12 quoted lines
>
> All steps looked quite sensibly done.
>
> >  - patch 5 will be replaced by/rebased on Matthew's work in 'config: allow user to
> >    know scope of config options', once 'config_scope_name' is available
>
> I expect that Matthew's topic would become solid enough after one
> more reroll to name the function back to config_scope_name(); after
> that, let's drop the step and instead fork this topic off of Matthew's
> topic to queue the remaining patches on top.
>
> Thanks.
-- 
Matthew Rogers
Previous: Junio C HamanoNext: Bert Wesarg
Message 13 of 14 in “remote rename/remove: improve handling of configuration values”
  1. 0/7 remote rename/remove: improve handling of configuration valuesBert Wesarg, Jan 24, 2020
  2. 2/7 remote: clean-up by returning early to avoid one indentationBert Wesarg, Jan 24, 2020
  3. 1/7 pull --rebase/remote rename: document and honor single-letter abbreviations rebase typesBert Wesarg, Jan 24, 2020
  4. 3/7 remote: clean-up config callbackBert Wesarg, Jan 24, 2020
  5. 5/7 config: make `scope_name` global as `config_scope_name`Bert Wesarg, Jan 24, 2020
  6. 4/7 remote rename/remove: handle branch.<name>.pushRemote config valuesBert Wesarg, Jan 24, 2020
  7. Johannes SchindelinJan 25, 2020
  8. Bert WesargJan 25, 2020
  9. Johannes SchindelinJan 26, 2020
  10. 7/7 remote rename/remove: gently handle remote.pushDefault configBert Wesarg, Jan 24, 2020
  11. 6/7 config: provide access to the current line numberBert Wesarg, Jan 24, 2020
  12. Junio C HamanoJan 24, 2020
  13. Matt RogersJan 25, 2020
  14. Bert WesargJan 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.