git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Derrick Stolee <derrickstolee@github.com>
To: Junio C Hamano <gitster@pobox.com>,
	git@vger.kernel.org, Phillip Wood <phillip.wood123@gmail.com>
Subject: ds/rebase-update-refs (was Re: What's cooking in git.git (Jun 2022, #02; Tue, 7))
Date: Wed, 8 Jun 2022 16:18:01 -0400	[thread overview]
Message-ID: <42863c70-0cc5-ce64-f8b9-a75cb6e1343c@github.com> (raw)
In-Reply-To: <xmqqwndsrm99.fsf@gitster.g>

On 6/7/2022 9:12 PM, Junio C Hamano wrote:

> * ds/rebase-update-refs (2022-06-07) 7 commits
>  - rebase: add rebase.updateRefs config option
>  - sequencer: implement 'update-refs' command
>  - rebase: add --update-refs option
>  - sequencer: add update-refs command
>  - sequencer: define array with enum values
>  - branch: add branch_checked_out() helper
>  - log-tree: create for_each_decoration()
> 
>  "git rebase" learns "--update-refs" to update the refs that point
>  at commits being rewritten so that they point at the corresponding
>  commits in the rewritten history.
> 
>  source: <3d7d3f656b4e93e8caa0d18d29c318ede956d1d7.1654634569.git.gitgitgadget@gmail.com>

One patch here generated enough subtleties to justify its own
topic [1]. In addition, Philip's feedback presented interesting
motivation to change the direction of this feature.

[1] https://lore.kernel.org/git/pull.1254.git.1654718942.gitgitgadget@gmail.com

I recommend ejecting this topic. I'll come back with a new
version of it (based on [1]) after the 2.37.0 release window.

Thanks,
-Stolee

      parent reply	other threads:[~2022-06-08 20:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-08  1:12 What's cooking in git.git (Jun 2022, #02; Tue, 7) Junio C Hamano
2022-06-08 16:56 ` Philippe Blain
2022-06-08 20:18 ` Derrick Stolee [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=42863c70-0cc5-ce64-f8b9-a75cb6e1343c@github.com \
    --to=derrickstolee@github.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=phillip.wood123@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.
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).