On Fri 16 Nov 2018 04:18:34 PM CET, Kevin Wolf wrote:
> Am 16.11.2018 um 16:03 hat Alberto Garcia geschrieben:
>> > I don't think anything needs a way to generally block graph changes
>> > around some node. We only need to prevent changes to very specific
>> > sets of edges. This is something tha
I feel bad for trimming your mail so much, but that's just because I've
read it and I agree. So, it's trimming of the good kind.
(Then again, when is trimming of a long mail ever bad?)
On 16.11.18 18:13, Kevin Wolf wrote:
[...]
> What we noted down about counters was more meaningful progress be
(I just wanted to reply quickly to this point, I'll read the rest of the
e-mail later)
On Fri 16 Nov 2018 05:34:08 PM CET, Max Reitz wrote:
> > GRAPH_MOD with the meaning that Berto suggested isn't weird or
> > complicated to understand. It's only the wrong tool because it
> > blocks more than we
Am 16.11.2018 um 17:34 hat Max Reitz geschrieben:
> On 16.11.18 16:51, Kevin Wolf wrote:
> > Am 16.11.2018 um 16:27 hat Max Reitz geschrieben:
> >> On 16.11.18 16:18, Kevin Wolf wrote:
> >>> Am 16.11.2018 um 16:03 hat Alberto Garcia geschrieben:
> > I don't think anything needs a way to general
On 16.11.18 16:51, Kevin Wolf wrote:
> Am 16.11.2018 um 16:27 hat Max Reitz geschrieben:
>> On 16.11.18 16:18, Kevin Wolf wrote:
>>> Am 16.11.2018 um 16:03 hat Alberto Garcia geschrieben:
> I don't think anything needs a way to generally block graph changes
> around some node. We only need
Am 16.11.2018 um 16:27 hat Max Reitz geschrieben:
> On 16.11.18 16:18, Kevin Wolf wrote:
> > Am 16.11.2018 um 16:03 hat Alberto Garcia geschrieben:
> >>> I don't think anything needs a way to generally block graph changes
> >>> around some node. We only need to prevent changes to very specific
> >
On 16.11.18 16:18, Kevin Wolf wrote:
> Am 16.11.2018 um 16:03 hat Alberto Garcia geschrieben:
>>> I don't think anything needs a way to generally block graph changes
>>> around some node. We only need to prevent changes to very specific
>>> sets of edges. This is something that the permission sys
On Fri 16 Nov 2018 04:03:12 PM CET, Alberto Garcia wrote:
>> top (T) -> intermediate (I) -> base (B)
>>
>> Now you commit from top to base. Clearly you don't want the backing
>> chain between top and base to change. So say you unshare the GRAPH_MOD
>> permission (implying that whenever a parent d
On 16.11.18 16:03, Alberto Garcia wrote:
> On Fri 16 Nov 2018 01:14:37 PM CET, Max Reitz wrote:
>> Permission system
>> =
>>
>> GRAPH_MOD
>> -
>>
>> We need some way for the commit job to prevent graph changes on its
>> chain while it is runni
Am 16.11.2018 um 16:03 hat Alberto Garcia geschrieben:
> > I don't think anything needs a way to generally block graph changes
> > around some node. We only need to prevent changes to very specific
> > sets of edges. This is something that the permission system just
> > cannot do.
>
> But what w
On Fri 16 Nov 2018 01:14:37 PM CET, Max Reitz wrote:
> Permission system
> =
>
> GRAPH_MOD
> -
>
> We need some way for the commit job to prevent graph changes on its
> chain while it is running. Our current blocker doesn’t do the job,
>
On 15.11.18 15:28, Alberto Garcia wrote:
> On Wed 14 Nov 2018 06:24:10 PM CET, Max Reitz wrote:
Permission system
=
GRAPH_MOD
-
We need some way for the commit job to prevent graph changes on its
chain while it is running. Our current
On 11/12/18 1:25 AM, Max Reitz wrote:
> This is what I’ve taken from two or three BoF-like get-togethers on
> blocky things. Amendments are more than welcome, of course.
>
>
>
> Permission system
> =
>
> GRAPH_MOD
> -
>
> We need some way for the commit job to prevent graph
On Wed 14 Nov 2018 06:24:10 PM CET, Max Reitz wrote:
>>> Permission system
>>> =
>>>
>>> GRAPH_MOD
>>> -
>>>
>>> We need some way for the commit job to prevent graph changes on its
>>> chain while it is running. Our current blocker doesn’t do the job,
>>> however. What to
On 13.11.18 16:12, Alberto Garcia wrote:
> On Sun 11 Nov 2018 11:25:00 PM CET, Max Reitz wrote:
>
>> Permission system
>> =
>>
>> GRAPH_MOD
>> -
>>
>> We need some way for the commit job to prevent graph changes on its
>> chain while it is running. Our current blocker does
On Sun 11 Nov 2018 11:25:00 PM CET, Max Reitz wrote:
> Permission system
> =
>
> GRAPH_MOD
> -
>
> We need some way for the commit job to prevent graph changes on its
> chain while it is running. Our current blocker doesn’t do the job,
> however. What to do?
>
> - We have
This is what I’ve taken from two or three BoF-like get-togethers on
blocky things. Amendments are more than welcome, of course.
Permission system
=
GRAPH_MOD
-
We need some way for the commit job to prevent graph changes on its
chain while it is running. Our current b
17 matches
Mail list logo
