On Sun, Feb 16, 2020 at 6:56 PM David Kastrup wrote:
> >> Han-Wen Nienhuys writes:
> >>
> >> > sorry, my mistake (another reason to move to different tooling.)
> >>
> >> I very strongly disagree. We don't want to move to a tooling where
> >> material that is untested in its context gets pushed
Han-Wen Nienhuys writes:
> On Sun, Feb 16, 2020 at 5:23 PM David Kastrup wrote:
>
>> Han-Wen Nienhuys writes:
>>
>> > sorry, my mistake (another reason to move to different tooling.)
>>
>> I very strongly disagree. We don't want to move to a tooling where
>> material that is untested in its co
On Sun, Feb 16, 2020 at 5:23 PM David Kastrup wrote:
> Han-Wen Nienhuys writes:
>
> > sorry, my mistake (another reason to move to different tooling.)
>
> I very strongly disagree. We don't want to move to a tooling where
> material that is untested in its context gets pushed to the resource
>
Han-Wen Nienhuys writes:
> sorry, my mistake (another reason to move to different tooling.)
I very strongly disagree. We don't want to move to a tooling where
material that is untested in its context gets pushed to the resource
everybody is dependent on. We have set up the staging system for a
sorry, my mistake (another reason to move to different tooling.)
It looks like savannah doesn't want people to do non-ff pushes; I've pushed
staging to be at the same commit.
[hanwen@localhost scm]$ git push origin HEAD:staging
Total 0 (delta 0), reused 0 (delta 0)
To ssh+git://git.sv.gnu.org/srv
Hello,
Master is now ahead of staging - this will break patchy staging right?
--snip--
input/regression/multi-measure-rest-reminder: a demo of user-defined
grobs master
author Han-Wen Nienhuys
Mon, 10 Feb 2020 21:10:35 + (22:10 +0100)
committer Han-Wen Nienhuys
Sun, 16 Feb
