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


Hi,

On Tue, Oct 23, 2012 at 11:06:44PM +0200, Michael Stahl wrote:
On 23/10/12 22:13, Ivan Timofeev wrote:
On 23.10.2012 23:43, Michael Stahl wrote:
On 23/10/12 21:28, Ivan Timofeev wrote:
On 23.10.2012 22:45, Libreoffice Gerrit user wrote:

$ git submodule update
fatal: reference is not a tree: c918f1d4242d9fd9a8de284e6b32b8c00e59debe
Unable to checkout 'c918f1d4242d9fd9a8de284e6b32b8c00e59debe' in
submodule path 'dictionaries'

what does that mean?

it means i should RTFM more and rely less on git to do the right thing,
which is apparently beyond its abilities :)

pushed that c918f1d4242d9fd9a8de284e6b32b8c00e59debe manually now...

thanks! Yeah, git behaves strange here... I've found git push
--recurse-submodules=<check|on-demand>, so git is smart enough, just
unconcerned.

thanks, that sounds useful; didn't work for me at first because those
submodules are on a detached head, not the master branch... after
fooling around with git rebase i got my commit on the master branch...

then i tried:

git push --recurse-submodules=on-demand --dry-run

which apparently helpfully already pushed the dictionaries submodule
onto the server, _despite_ the --dry-run :-/

What I do is

git push origin HEAD:master

in the submodule _followed_ by

git push

in core. I admit it could be a bit easier, but I find it good enough for
occasional use.

D.

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.