Closed shibumi closed 6 years ago
Works for me. Looks like you somehow have color codes in your branch names. In addition, all failing branches are elsewhere valid branches that you already have tracked.
mhhh funny. Where does these color codes come from?
git maybe? I have no idea
I have set color.branch = always
in my gitconfig. Thats possibly the reason for this behaviour. Shouldn't asp filter the color codes? Does this have any impact on asp?
Disable it and find out? Perhaps I should override that in asp's git config
without my gitconfig
I get the following output:
==> updating remote 'packages'
From git://git.archlinux.org/svntogit/packages
* branch packages/gcc -> FETCH_HEAD
* branch packages/mutt -> FETCH_HEAD
* branch packages/quagga -> FETCH_HEAD
==> updating remote 'community'
From git://git.archlinux.org/svntogit/community
* branch packages/cowfortune -> FETCH_HEAD
* branch packages/dolphin-emu -> FETCH_HEAD
* branch packages/linux-hardened -> FETCH_HEAD
* branch packages/mbedtls -> FETCH_HEAD
* branch packages/nrpe -> FETCH_HEAD
* branch packages/python-magic -> FETCH_HEAD
So it's definitly my .gitconfig. Overwriting it in your asp git config is a good idea :)
There seems to be a bug with the branch names: