On Fri, Jul 13, 2012 at 9:29 AM, Stephan Bergmann <sbergman@redhat.com> wrote:
Machine cannot determine dependency among patches, and I see no reason here
to try to do so nevertheless, with whatever heuristic. Rather, I prefer if
the user has to mark patches as dependent or not. If the current interface
makes it too easy for users to erroneously mark patches as dependent, then
we should consider redesigning the interface.
Think of it as a graph.
A set of patch based on a known base is presumed to be
order-dependant, because they _could_ and typically are.
so when gerrit receive a set of new patches on top of a given base he
rightly assume that their order _is_ important.
I know this is a problem for those whose workflow involve piling a
bunch of unrelated patches and then pushing once a day or so.
There are some scripting that has and can be done to accommodate this workflow.
Norbert
Stephan
_______________________________________________
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice
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.