On Mon, Mar 12, 2012 at 2:19 PM, Miklos Vajna <vmiklos@suse.cz> wrote:
Hi Norbert,
Is this really an issue? Right now only the relevant repos are cloned
(e.g. by default translations is not cloned), if you do the same with
submodule init, translations could be a submodule as well. Or did I miss
something?
you are right...
that would means that ./g remain but is adapted to update the
appropriate submodules based on bin/git-repos
I could each ./g pull to update the submodules after pulling core...
and other user-friendly stuff ...
I need to play a bit more with it
Just to be clear: this is true for any non-core commit, not only merges.
only to the extent that you care for that commit to be visible in core...
practically if you are going to push a patch series on binfilter for
instance, there is no reason to upgrade core at every commits.
but yes you are right it is not only 'merge'
Norbert
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.