On Wed, Oct 24, 2012 at 10:10 AM, Stephan Bergmann <sbergman@redhat.com> wrote:
So when you have a core commit A and a submodule commit B that logically
belong together, with the above recipe the end result on the server will no
longer reflect that, as it "ties" B to an "artificial" core commit C
preceding A, instead of keeping B "tied" to A.
the rational here is: pushing in submodule and forgetting a commit in
the super module is a common anti-pattern, so gerrit automate that.
and submodules A and B are presumably independent (the whole point of
submodules was, in their intent to allow for such loosely connected
section of code), so a commit in either should not be related in a
commit to the other.
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.