Re: [PATCH v6 09/10] builtin/history: split handling of ref updates into two phases
- From
Christian Couder <christian.couder@gmail.com>
- Date
- Jun 25, 2026, 13:37 UTC
- Message-ID
- <CAP8UFD1evTZqj1ymW9g5g2RmMkYMaE0rPa0Hzt+irH94M6LD6A@mail.gmail.com>
- In-Reply-To
- <20260615-b4-pks-history-drop-v6-9-2e329e536d78@pks.im>
On Mon, Jun 15, 2026 at 3:56 PM Patrick Steinhardt <ps@pks.im> wrote:
Show 9 quoted lines
> @@ -414,14 +389,43 @@ static int handle_reference_updates(struct rev_info *revs, > !detached_head) > continue; > > + ALLOC_GROW(result->updates, result->updates_nr + 1, result->updates_alloc); > + result->updates[result->updates_nr].refname = xstrdup(decoration->name); > + result->updates[result->updates_nr].old_oid = original->object.oid; > + result->updates[result->updates_nr].new_oid = rewritten->object.oid; > + result->updates_nr++;
It looks like this duplicates what replay_result_queue_update() from replay.c does.
> + }