On Mon, Aug 28, 2023 at 05:47:17PM -0400, Jeff King wrote: > Note that we could also drop this parameter entirely, as the function is > always called directly, and not as a callback that has to conform to > some external interface. But since we'd eventually want to use the > repository parameter, let's leave it in place to avoid disrupting the > callers twice. Yeah, I think that this (and the discussion on the previous patch) are hinting that we should consider dropping the repository argument more broadly throughout the sequencer API, since we can often use `opts->revs->repo` in its place. But we can definitely leave that for another day ;-). In the meantime, this patch LGTM. Thanks, Taylor
