> On Jan 27, 2020, at 2:12 PM, George Dunlap wrote:
>
> I have drafted an explicit policy on what is (generally) required to
> check a patch in. It's been through several rounds, and v4 has been
> acked [1].
>
> I've had informal assent from all committers, but just to dot all our
> i's and
Hi all,
+1.
Cheers,
On 27/01/2020 14:12, George Dunlap wrote:
I have drafted an explicit policy on what is (generally) required to
check a patch in. It's been through several rounds, and v4 has been
acked [1].
I've had informal assent from all committers, but just to dot all our
i's and
On Mon, Jan 27, 2020 at 03:27:40PM +0100, Jan Beulich wrote:
> On 27.01.2020 15:12, George Dunlap wrote:
> > I have drafted an explicit policy on what is (generally) required to
> > check a patch in. It's been through several rounds, and v4 has been
> > acked [1].
> >
> > I've had informal
On 27/01/2020, 14:12, "George Dunlap" wrote:
I have drafted an explicit policy on what is (generally) required to
check a patch in. It's been through several rounds, and v4 has been
acked [1].
I've had informal assent from all committers, but just to dot all our
i's
On 27.01.2020 15:12, George Dunlap wrote:
> I have drafted an explicit policy on what is (generally) required to
> check a patch in. It's been through several rounds, and v4 has been
> acked [1].
>
> I've had informal assent from all committers, but just to dot all our
> i's and cross all our
I have drafted an explicit policy on what is (generally) required to
check a patch in. It's been through several rounds, and v4 has been
acked [1].
I've had informal assent from all committers, but just to dot all our
i's and cross all our t's, it's probably worth having a vote of the
