Date: Sun, 1 Sep 2019 19:42:29 +0200 From: Hans Petter Selasky <hps@selasky.org> To: Warner Losh <imp@bsdimp.com>, Ed Maste <emaste@freebsd.org> Cc: FreeBSD Hackers <freebsd-hackers@freebsd.org>, Li-Wen Hsu <lwhsu@freebsd.org>, fcp@freebsd.org Subject: Re: FCP 20190401-ci_policy: CI policy Message-ID: <44a1a905-9b35-620b-281c-cdbbee538bed@selasky.org> In-Reply-To: <CANCZdfoWAuSCKqFwWsnXTmznyuazHfy0tAfgZEv1m92MeSHAEg@mail.gmail.com> References: <CAKBkRUwKKPKwRvUs00ja0%2BG9vCBB1pKhv6zBS-F-hb=pqMzSxQ@mail.gmail.com> <20190829114057.GZ71821@kib.kiev.ua> <CAPyFy2BNrFfZ1PHaLesW%2Bu7YmbhC7mtiZ%2BBsYrqYE0J7KdagaA@mail.gmail.com> <20190830065534.GC71821@kib.kiev.ua> <CAPyFy2CXVMEXZx0u9b0p_CVaD_gu8Gyzvud3KwEDciq83a2_8A@mail.gmail.com> <73111.1567263258@kaos.jnpr.net> <CANCZdfqJzpxj7-P7XN7GEsECEA%2BLaUq6yQJ98OQUp_gXX9FF9Q@mail.gmail.com> <CAPyFy2CdddbDZYNod1ze1Z2iMyggSPP5kQV6ePeKSRQntezZEQ@mail.gmail.com> <CANCZdfoWAuSCKqFwWsnXTmznyuazHfy0tAfgZEv1m92MeSHAEg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, If the fallouts could be better organized through some simple guidelines, that would be more accepted I think: 1) Don't commit stuff before going off work. Even though a change looks innocent, it might break something and you'll need to fix it. 2) Organize big changes going into the kernel, to ease debugging and getting things back on track again. 3) If your patch is risky, commit it on a Monday. Don't wait until Friday. Failure to follow the rules may have consequences like other senior developers kicking in and doing temporary reverts until issues are resolved. --HPS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44a1a905-9b35-620b-281c-cdbbee538bed>