Re: [PATCH v2 0/7] remote rename/remove: improve handling of configuration values
- From
Bert Wesarg <bert.wesarg@googlemail.com>
- Date
- Jan 27, 2020, 06:50 UTC
- Message-ID
- <CAKPyHN0giHdGeeTRe6ZQL14d=1GkkC24Zu142gTuDAZhqtittQ@mail.gmail.com>
- In-Reply-To
- <CAOjrSZtT0bX=hhH=OZdA80T_Thgn9drG66xcVMYjo7Q=5Cw_Bw@mail.gmail.com>
Junio,
On Sat, Jan 25, 2020 at 1:39 AM Matt Rogers <mattr94@gmail.com> wrote:
> > Yeah, I just resubmitted so you should be good to go
I can resend the rebased topic at any time. And as I don't see that you picked up by latest re-roll (cover in cover.1579857394.git.bert.wesarg@googlemail.com) in into bw/remote-rename-update-config yet, I think it makes sense to do this now.
Best, Bert
Show 19 quoted lines
> > On Fri, Jan 24, 2020 at 4:10 PM Junio C Hamano <gitster@pobox.com> wrote: > > > > All steps looked quite sensibly done. > > > > > - patch 5 will be replaced by/rebased on Matthew's work in 'config: allow user to > > > know scope of config options', once 'config_scope_name' is available > > > > I expect that Matthew's topic would become solid enough after one > > more reroll to name the function back to config_scope_name(); after > > that, let's drop the step and instead fork this topic off of Matthew's > > topic to queue the remaining patches on top. > > > > Thanks. > > > > -- > Matthew Rogers