[dev] pulling Horde sources
Sebastian Birnbach
birnbacs at gmail.com
Sat Jan 5 11:19:30 UTC 2019
Removing the 'shallow' option in the conf.php unfortunately did not change
anything.
Vilma was just an example, corresponding messages get output for each and
every repository.
So it's 169 'INFO Repository' messages, followed by 169 'INFO Switching'
messages and 2 * 169 'Error pathspec' messages.
The 'git pass through' command does not yield much information on branches.
I cannot see other branches but 'master' on the github portal either.
horde-git-tools/bin/horde-git-tools git run branch
[ INFO ] Handling git command.
Please note that the Horde sources got copied (cloned) all right, it's the
checkout command that is giving me trouble.
I'm a bit confused what is supposed to happen. A 'git checkout' is the
definition which branch of a repository I am going to work upon, right?
Everything that is not part of the selected branch should become invisible,
yes?
Seb.
Am Sa., 5. Jan. 2019 um 06:07 Uhr schrieb Ralf Lang <lang at b1-systems.de>:
> hi Sebastian
> from memory:
>
> remove the "shallow" option before initial Checkout or adding a large
> number to shallow option.
>
> there is some "run arbitrary git command" mode where you can run git fetch
> to get the branches from server before doing git checkout
>
> some repos may not have a framework5_2 branch because they are alpha ever
> since. vilma is something like postfixadmin, i doubt you will need it.
> --
> Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.
More information about the dev
mailing list