Date: prev next · Thread: first prev next last
2013 Archives by date, by thread · List index


Norbert Thiebaud wrote:
The dev-ML is to discuss code.
code come as patch, and preferably as gerrit patch... so seing the
patch that are proposed via gerrit is the core function of the ML,
just like before gerrit they where posted to the ML .

Yup.

If we remove all the [PATCH] from the ML, what is left ? a
dev-discuss list ?

It is already now the case that there is a disconnect between
discussing code, or a concrete problem, and the subsequent gerrit
patch submission (case in point: https://gerrit.libreoffice.org/3699,
https://gerrit.libreoffice.org/3698 and Noel Grandin's conversion
operators for UNO thread), I'm very hesitant to widen that gap.

Devil's advocate question: with that two-list proposal, where to
discuss a given patch? ;)

Cheers,

-- Thorsten

Attachment: signature.asc
Description: Digital signature


Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.