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

From: Rubén Justo <rjusto@gmail.com>
Date: Dec 2, 2022, 22:01 UTC
Message-ID: <a0237e20-a9fc-0265-c0ab-a9d5373a3547@gmail.com>
In-Reply-To: <e0c876db-a230-dfa4-f4e1-5296ffe62c37@github.com>

On 2/12/22 21:11, Victoria Dye wrote:> Rubén Justo wrote:

Show 21 quoted lines

>> 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
>>>
>>>  Fix a pair of bugs in 'git branch'.
>>>  
>>>  Waiting for review discussion to settle.
>>>  source: <f0b2d46c-2e9c-2630-2870-8ed550dd1606@gmail.com>
>>>
>> 
>> 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.
> 
> Thanks!

Thank you.

Show 10 quoted lines

> 
>> 
>> Un saludo.
>> Rubén.
> 
> P.S. I think there may be something strange about your email editor. For
> some reason, every line is padded out with spaces to 200 characters. Not a
> big deal, but your replies might render with unexpected line spacing in some
> email clients.
>

Sorry. I edited in another box and copied directly from the window. Thanks for notifying.