Message ID | pull.1497.v3.git.git.1687290231.gitgitgadget@gmail.com (mailing list archive) |
---|---|
Headers | show |
Series | config: remove global state from config iteration | expand |
"Glen Choo via GitGitGadget" <gitgitgadget@gmail.com> writes: > Junio: I rebased this onto a newer "master". I assume this is a noop for > you - I noticed that the RFC versions weren't applied anyway (good). It would be a noop only if I do not queue this iteration. I've reviewed them in its current shape, but it seems to cause too many conflicts even when merged to 'next', let alone 'seen', with interactions with topics in flight: * ds/add-i-color-configuration-fix (easy) * ps/fetch-cleanups (easy but messy) * vd/worktree-config-is-per-repository (moderately messy) some of which may have graduated to 'master' in the meantime, so it might not be a bad idea to rebase on a more recent 'master' after you collect and adjust for review comments on v3. Thanks.
Junio C Hamano <gitster@pobox.com> writes: > I've reviewed them in its current shape, but it seems to cause too > many conflicts even when merged to 'next', let alone 'seen', with > interactions with topics in flight: > > * ds/add-i-color-configuration-fix (easy) > * ps/fetch-cleanups (easy but messy) > * vd/worktree-config-is-per-repository (moderately messy) Ah, sorry. I ran some trial merges against these before I sent out v3, but I forgot as I sent this out. Not queueing this version sounds fine. > some of which may have graduated to 'master' in the meantime, so it > might not be a bad idea to rebase on a more recent 'master' after > you collect and adjust for review comments on v3. Sounds good. I suppose it would also be worthwhile to base it on conflicting topics queued for 'next'.
Glen Choo <chooglen@google.com> writes: > Junio C Hamano <gitster@pobox.com> writes: > > > I've reviewed them in its current shape, but it seems to cause too > > many conflicts even when merged to 'next', let alone 'seen', with > > interactions with topics in flight: > > > > * ds/add-i-color-configuration-fix (easy) > > * ps/fetch-cleanups (easy but messy) > > * vd/worktree-config-is-per-repository (moderately messy) > > Ah, sorry. I ran some trial merges against these before I sent out v3, > but I forgot as I sent this out. Not queueing this version sounds fine. > > > some of which may have graduated to 'master' in the meantime, so it > > might not be a bad idea to rebase on a more recent 'master' after > > you collect and adjust for review comments on v3. > > Sounds good. I suppose it would also be worthwhile to base it on > conflicting topics queued for 'next'. Glen, if you can, rebase the patches *before* updating them based on my comments so that it's easier for reviewers to see if my comments have been addressed. (My comments are minor, so they should still be relevant even after rebasing.) Overall the patch set looks good aside from some minor comments that I've given as replies to the patches.
Jonathan Tan <jonathantanmy@google.com> writes: > Glen Choo <chooglen@google.com> writes: >> Junio C Hamano <gitster@pobox.com> writes: >> >> > I've reviewed them in its current shape, but it seems to cause too >> > many conflicts even when merged to 'next', let alone 'seen', with >> > interactions with topics in flight: >> > >> > * ds/add-i-color-configuration-fix (easy) >> > * ps/fetch-cleanups (easy but messy) >> > * vd/worktree-config-is-per-repository (moderately messy) >> >> Ah, sorry. I ran some trial merges against these before I sent out v3, >> but I forgot as I sent this out. Not queueing this version sounds fine. >> >> > some of which may have graduated to 'master' in the meantime, so it >> > might not be a bad idea to rebase on a more recent 'master' after >> > you collect and adjust for review comments on v3. >> >> Sounds good. I suppose it would also be worthwhile to base it on >> conflicting topics queued for 'next'. > > Glen, if you can, rebase the patches *before* updating them based on my > comments so that it's easier for reviewers to see if my comments have > been addressed. (My comments are minor, so they should still be relevant > even after rebasing.) > > Overall the patch set looks good aside from some minor comments that > I've given as replies to the patches. Thanks for a quick review (and thank you, Glen, for working on it).
Jonathan Tan <jonathantanmy@google.com> writes: >> Sounds good. I suppose it would also be worthwhile to base it on >> conflicting topics queued for 'next'. > > Glen, if you can, rebase the patches *before* updating them based on my > comments so that it's easier for reviewers to see if my comments have > been addressed. (My comments are minor, so they should still be relevant > even after rebasing.) Good idea. Fortunately, I already have that prepared, so there's not much extra work for me.