On Mon, Mar 12, 2012 at 06:44:40PM -0500, Norbert Thiebaud <nthiebaud@gmail.com> wrote:
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
Hm, I'm not exactly sure. Did you search for submodule in 'man
git-config'? There is a nice submodule.<name>.ignore, I can imagine
setting that can avoid ./g pull, given that 'git pull' by default
updates submodules as well, if the submodule reference is updated.
(I mean setting where you enable git hooks, etc.)
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.
Sure, from a user's point of view, best to update core.git before push,
not after every commit.
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.