On Wed, Aug 29, 2012 at 08:52:27AM -0700, Junio C Hamano wrote:
> (I won't comment on the other parts in this discussion).
which is kinda unfortunate. ;)
> Oswald Buddenhagen <o...@kde.org> writes:
> > i did exacty that. the tags are *still* not populated - git just tries
> > very hard to treat them specially.
> git push $over_there 'refs/*:refs/remotes/mine/*'
> push your tag v1.0 to refs/remotes/mine/v1.0 over there? The
> version of git I ship seems to do this just fine.
as i wrote before, i'm pulling, not pushing, so any differences could be
blamed on that (or git version 18.104.22.168.g948900e).
anyway, it seems this new version does fetch the tags under the remotes'
namespaces, after all - but it still imports them into the global tag
namespace as well, which of course makes a mess with the duplicated
and for many repos i'm getting something like this (this is kinda new):
remote: Counting objects: 62375, done.
remote: Compressing objects: 100% (28049/28049), done.
remote: Total 55704 (delta 45280), reused 36646 (delta 27368)
Receiving objects: 100% (55704/55704), 16.76 MiB | 4.94 MiB/s, done.
Resolving deltas: 100% (45280/45280), completed with 3017 local objects.
fatal: bad object 90f0f499ec5953d60d616a2ff541ecaf8b0c31a2
error: ../qt5/qtbase did not send all necessary objects
both the aggregator and the fetched repos run cleanly through fsck.
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html