Re: fsck --full is Ok, but clones are not, "missing commits"?!
- From
Johannes Sixt <j.sixt@viscovery.net>
- Date
- Apr 18, 2008, 08:55 UTC
- Message-ID
- <48086200.5020600@viscovery.net>
- In-Reply-To
- <a537dd660804180141h25b7f8e2yf7283f63d49521e6@mail.gmail.com>
Brian Foster schrieb:
Show 27 quoted lines
> that seemingly bogus `check-ref-format' argument comes > from the pipeline (where ref=master): > > git for-each-ref --format='%(refname)' | grep /"$ref" > i.e.: > git for-each-ref --format='%(refname)' | grep /master > > so... > $ git for-each-ref --format='%(refname)' > refs/heads/master > refs/remotes/origin/HEAD > refs/remotes/origin/master > refs/tags/linux-2.6.15 > refs/tags/linux-usip-v2.6.15 > [ ... ] > $ > > note two names match the RE `/master', hence the bogus > argument. the reason for that seems to be (this is a > guess!) that `rev-parse' is *not* being run as: > > git rev-parse --no-flags --revs-only \ > --symbolic-full-name --default HEAD --branches > > as I _think_ you are claiming it should be, but as: > > git rev-parse --revs-only --symbolic --branches
One of the changes since v.1.5.3 was to get rid of this bogus grep. Can you install a newer git?
-- Hannes