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

Re: [PATCH v2] remote rename: rename branch.<name>.pushRemote config values too

From
Junio C Hamano <gitster@pobox.com>
Date
Jan 17, 2020, 21:24 UTC
Message-ID
<xmqqo8v1dbeb.fsf@gitster-ct.c.googlers.com>
In-Reply-To
<CAKPyHN2RwpWhBkTUwERSns0B0Vg7r7CTmhe8p0mZRNeNw4Aagw@mail.gmail.com>
Bert Wesarg <bert.wesarg@googlemail.com> writes:
> can you give me an heads up about your expected number of patches for
> this clean up. Rather detailed or just one?
That's up to the contributor X-<.

I would expect that some folks can write it up as a single patch and still keep it easily understandable, and others might have trouble explaining what they did well to the others and may need to split them into a few pieces.

Previous: Bert WesargNext: Johannes Schindelin
Message 13 of 15 in “remote: rename also remotes in the branch.<name>.pushRemote config”
  1. remote: rename also remotes in the branch.<name>.pushRemote configBert Wesarg, Jan 16, 2020
  2. Junio C HamanoJan 16, 2020
  3. remote rename: rename branch.<name>.pushRemote config values tooBert Wesarg, Jan 17, 2020
  4. Johannes SchindelinJan 17, 2020
  5. Bert WesargJan 17, 2020
  6. Johannes SchindelinJan 17, 2020
  7. Bert WesargJan 17, 2020
  8. Johannes SchindelinJan 20, 2020
  9. Bert WesargJan 20, 2020
  10. Johannes SchindelinJan 20, 2020
  11. Junio C HamanoJan 17, 2020
  12. Bert WesargJan 17, 2020
  13. Junio C HamanoJan 17, 2020
  14. Johannes SchindelinJan 17, 2020
  15. Johannes SchindelinJan 17, 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.