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
Subject: ds/rebase-update-re (was Re: What's cooking in git.git (Jul 2022, #01; Fri, 1))
Date: Mon, 4 Jul 2022 07:15:02 -0600	[thread overview]
Message-ID: <15631ea2-6722-fd24-c8a6-0cee638b0602@github.com> (raw)
In-Reply-To: <xmqqo7y85t44.fsf@gitster.g>

On 7/1/22 5:08 PM, Junio C Hamano wrote:

> * ds/rebase-update-ref (2022-06-28) 8 commits
>  - rebase: add rebase.updateRefs config option
>  - rebase: update refs from 'update-ref' commands
>  - rebase: add --update-refs option
>  - sequencer: add update-ref command
>  - sequencer: define array with enum values
>  - rebase-interactive: update 'merge' description
>  - branch: consider refs under 'update-refs'
>  - t2407: test branches currently using apply backend
>  (this branch uses ds/branch-checked-out.)
> 
>  "git rebase -i" learns to update branches whose tip appear in the
>  rebased range.
> 
>  Will merge to 'next'?
>  source: <pull.1247.v3.git.1656422759.gitgitgadget@gmail.com>

Please expect at least one more re-roll. Here are the things I
intend to fix in the next re-roll, which should arrive sometime
this week.

* Some commit message tweaks.
* Actually interrupt 'git bisect' and 'git rebase' in the tests.
* Be careful to update the update-refs file when the user edits
  the todo file.
* Consider storing the "before" values in the update-refs file
  and removing refs whose update-ref steps were removed by the
  user.
* Elijah had a question about focusing on "pick" actions, not
  "fixup" or "squash" steps. This might be worth marking the
  option as experimental so we have flexibility in changing the
  behavior as new workflows are tested against this option.
* Elijah also had some optimization ideas, but I'm not sure if
  we should prioritize them here or have them as future
  improvements after the feature is stable.

Thanks,
-Stolee


  parent reply	other threads:[~2022-07-04 13:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-01 23:08 What's cooking in git.git (Jul 2022, #01; Fri, 1) Junio C Hamano
2022-07-04  8:12 ` gc/submodule-use-super-prefix & ab/submodule-cleanup (was: What's cooking in git.git (Jul 2022, #01; Fri, 1)) Ævar Arnfjörð Bjarmason
2022-07-06 16:57   ` Glen Choo
2022-07-04 13:15 ` Derrick Stolee [this message]
2022-07-04 15:59   ` ds/rebase-update-re (was " Junio C Hamano
2022-07-04 16:58   ` Elijah Newren
2022-07-04 20:17     ` Derrick Stolee
2022-07-05  1:31 ` en/merge-dual-dir-renames-fix (Was: " Elijah Newren
2022-07-06 17:56 ` gc/bare-repo-discovery (was " Glen Choo
2022-07-06 22:15   ` 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

  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=15631ea2-6722-fd24-c8a6-0cee638b0602@github.com \
    --to=derrickstolee@github.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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).