From: Derrick Stolee <derrickstolee@github.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: ds/rebase-update-ref (was Re: What's cooking in git.git (Jul 2022, #04; Wed, 13))
Date: Thu, 14 Jul 2022 08:11:39 -0400 [thread overview]
Message-ID: <c77648aa-b74b-008b-0bc0-bd6f95eedf2f@github.com> (raw)
In-Reply-To: <xmqq7d4g8onl.fsf@gitster.g>
On 7/13/22 9:32 PM, Junio C Hamano wrote:
> * ds/rebase-update-ref (2022-07-12) 13 commits
> - sequencer: notify user of --update-refs activity
> - sequencer: ignore HEAD ref under --update-refs
> - rebase: add rebase.updateRefs config option
> - sequencer: rewrite update-refs as user edits todo list
> - 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
> - t2407: test bisect and rebase as black-boxes
> - Merge branch 'ds/branch-checked-out' into ds/rebase-update-ref
>
> "git rebase -i" learns to update branches whose tip appear in the
> rebased range.
>
> Expecting a reroll.
> cf. <15631ea2-6722-fd24-c8a6-0cee638b0602@github.com>
> source: <pull.1247.v4.git.1657631225.gitgitgadget@gmail.com>
It looks like you've picked up the latest re-roll (v4), so this
status is a little stale.
Thanks,
-Stolee
next prev parent reply other threads:[~2022-07-14 12:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-14 1:32 What's cooking in git.git (Jul 2022, #04; Wed, 13) Junio C Hamano
2022-07-14 12:11 ` Derrick Stolee [this message]
2022-07-14 16:35 ` ds/rebase-update-ref (was Re: What's cooking in git.git (Jul 2022, #04; Wed, 13)) Junio C Hamano
2022-07-15 13:40 ` ab/squelch-empty-fsync-traces & hx/unpack-streaming bug (was: " Ævar Arnfjörð Bjarmason
2022-07-16 12:23 ` Han Xin
2022-07-17 3:46 ` en/merge-restore-to-pristine (Was: " Elijah Newren
2022-07-17 16:58 ` ZheNing Hu
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=c77648aa-b74b-008b-0bc0-bd6f95eedf2f@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).