From: Victoria Dye <vdye@github.com>
To: "Rubén Justo" <rjusto@gmail.com>,
"Junio C Hamano" <gitster@pobox.com>,
git@vger.kernel.org
Subject: Re: What's cooking in git.git (Dec 2022, #01; Thu, 1)
Date: Fri, 2 Dec 2022 12:11:16 -0800 [thread overview]
Message-ID: <e0c876db-a230-dfa4-f4e1-5296ffe62c37@github.com> (raw)
In-Reply-To: <c489ad32-1308-06c9-0c92-6e39d1f82a4b@gmail.com>
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
>>
>> 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!
>
> 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.
next prev parent reply other threads:[~2022-12-02 20:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-01 12:23 What's cooking in git.git (Dec 2022, #01; Thu, 1) Junio C Hamano
2022-12-01 22:45 ` Rubén Justo
2022-12-02 20:11 ` Victoria Dye [this message]
2022-12-02 22:01 ` Rubén Justo
2022-12-05 3:26 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e0c876db-a230-dfa4-f4e1-5296ffe62c37@github.com \
--to=vdye@github.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=rjusto@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.