git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Victoria Dye <vdye@github.com>
Cc: "Rubén Justo" <rjusto@gmail.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Dec 2022, #01; Thu, 1)
Date: Mon, 05 Dec 2022 12:26:01 +0900	[thread overview]
Message-ID: <xmqq359usf92.fsf@gitster.g> (raw)
In-Reply-To: <e0c876db-a230-dfa4-f4e1-5296ffe62c37@github.com> (Victoria Dye's message of "Fri, 2 Dec 2022 12:11:16 -0800")

Victoria Dye <vdye@github.com> writes:

> 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.

      parent reply	other threads:[~2022-12-05  3:26 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
2022-12-02 22:01     ` Rubén Justo
2022-12-05  3:26     ` Junio C Hamano [this message]

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqq359usf92.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=rjusto@gmail.com \
    --cc=vdye@github.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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).