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

Re: What's cooking in git.git (Dec 2022, #01; Thu, 1)

From
Junio C Hamano <gitster@pobox.com>
Date
Dec 5, 2022, 03:26 UTC
Message-ID
<xmqq359usf92.fsf@gitster.g>
In-Reply-To
<e0c876db-a230-dfa4-f4e1-5296ffe62c37@github.com>
Victoria Dye <vdye@github.com> writes:
Show 14 quoted lines
> Rubén Justo wrote:
>> On 01-dic-2022 21:23:40, Junio C Hamano wrote:
>>> * rj/branch-copy-and-rename (2022-11-17) 2 commits
>>>  - branch: clear target branch configuration before copying or renaming
>>>  - branch: force-copy a branch to itself via @{-1} is a no-op
>>> ...
>> We can drop the first commit (branch: clear target branch configuration
>> before copying or renaming) as it needs a better approach.  But we can
>> keep the other (branch: force-copy a branch to itself via @{-1} is a
>> no-op), there were no complaints about it, I think.
>
> Agreed. I think "branch: clear target branch configuration before copying or
> renaming" is probably worth revisiting at some point, but "branch:
> force-copy a branch to itself via @{-1} is a no-op" looks fine to be as-is.

OK, let's discard the tip one and mark the other one to be merged to 'next'.

Thanks, both.
Previous: Rubén Justo
Message 5 of 5 in “What's cooking in git.git (Dec 2022, #01; Thu, 1)”
  1. Junio C HamanoDec 1, 2022
  2. Rubén JustoDec 1, 2022
  3. Victoria DyeDec 2, 2022
  4. Rubén JustoDec 2, 2022
  5. Junio C HamanoDec 5, 2022

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.