[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Grow heap aggressively during music interpretation (issue 561390043
From: |
David Kastrup |
Subject: |
Re: Grow heap aggressively during music interpretation (issue 561390043 by address@hidden) |
Date: |
Mon, 03 Feb 2020 11:34:14 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) |
Han-Wen Nienhuys <address@hidden> writes:
> On Sun, Feb 2, 2020 at 11:47 PM <address@hidden> wrote:
>>
>> On 02/02/2020 22:33, Han-Wen Nienhuys wrote:
>> > For me, juggling 15 different outstanding code reviews at the same
>> > time is the bane of the current development process.
>>
>> what do you suggest?
>
> I think we should move to a git-based code review tool; Github, Gitlab
> or Gerrit. Gerrit is probably the closest to the current workflow.
>
> Then, you could push an entire branch with several commits for review.
>
> The state of the change could be administered within the code review
> itself, so we don't need to keep tools in sync with each other.
I don't see how this changes the problem of a controversial patch
blocking the progress of dependent patches while the controversy is not
yet resolved.
--
David Kastrup
- Re: Grow heap aggressively during music interpretation (issue 561390043 by address@hidden), (continued)
- Re: Grow heap aggressively during music interpretation (issue 561390043 by address@hidden), Han-Wen Nienhuys, 2020/02/02
- Re: Grow heap aggressively during music interpretation (issue 561390043 by address@hidden), pkx166h, 2020/02/02
- Re: Grow heap aggressively during music interpretation (issue 561390043 by address@hidden), Han-Wen Nienhuys, 2020/02/03
- Re: Grow heap aggressively during music interpretation (issue 561390043 by address@hidden), Han-Wen Nienhuys, 2020/02/03
- Re: Grow heap aggressively during music interpretation (issue 561390043 by address@hidden), Han-Wen Nienhuys, 2020/02/03
- Re: Grow heap aggressively during music interpretation (issue 561390043 by address@hidden), David Kastrup, 2020/02/03
- Re: Grow heap aggressively during music interpretation (issue 561390043 by address@hidden), Dan Eble, 2020/02/03
- Re: Grow heap aggressively during music interpretation (issue 561390043 by address@hidden), David Kastrup, 2020/02/03
- Re: Grow heap aggressively during music interpretation (issue 561390043 by address@hidden), Jonas Hahnfeld, 2020/02/03
- Re: Grow heap aggressively during music interpretation (issue 561390043 by address@hidden), Han-Wen Nienhuys, 2020/02/03
- Re: Grow heap aggressively during music interpretation (issue 561390043 by address@hidden),
David Kastrup <=
Re: Grow heap aggressively during music interpretation (issue 561390043 by address@hidden), jonas . hahnfeld, 2020/02/04
Re: Grow heap aggressively during music interpretation (issue 561390043 by address@hidden), jonas . hahnfeld, 2020/02/05
- Re: Grow heap aggressively during music interpretation (issue 561390043 by address@hidden), Han-Wen Nienhuys, 2020/02/05
- Re: Grow heap aggressively during music interpretation (issue 561390043 by address@hidden), Han-Wen Nienhuys, 2020/02/05
- Re: Grow heap aggressively during music interpretation (issue 561390043 by address@hidden), David Kastrup, 2020/02/05
- Re: Grow heap aggressively during music interpretation (issue 561390043 by address@hidden), Jonas Hahnfeld, 2020/02/06
- Re: Grow heap aggressively during music interpretation (issue 561390043 by address@hidden), Han-Wen Nienhuys, 2020/02/07
- Re: Grow heap aggressively during music interpretation (issue 561390043 by address@hidden), Han-Wen Nienhuys, 2020/02/07
- Re: Grow heap aggressively during music interpretation (issue 561390043 by address@hidden), David Kastrup, 2020/02/07