From: Kent Fredric <kentfredric@gmail.com>
To: Heiko Voigt <hvoigt@hvoigt.net>
Cc: git@vger.kernel.org
Subject: Re: IRC discussion re: submodules & missing refs/heads/master
Date: Thu, 19 Apr 2012 09:22:12 +1200 [thread overview]
Message-ID: <CAATnKFCoE6XXTB48Mvq-ay-j-1gyxxPBUvLM+REFWHLCsrTsVQ@mail.gmail.com> (raw)
In-Reply-To: <20120418211426.GA6920@book.hvoigt.net>
On 19 April 2012 09:14, Heiko Voigt <hvoigt@hvoigt.net> wrote:
> From the subject I deduce that you have a some problem involving
> submodules. Could you please clearly summarise what you found and
> possibly provide a recipe (script snippet) how to reproduce the issue?
>
The transcript was provided for context, after the transcript are
details of the problem and solution.
Summarised is as follows:
on 1.7.8.5 , running "git gc" while inside a submodule path removes
refs/heads/master for that submodule in ~/.git/modules , and for
some reason, sub-modules still require those files to work properly at
1.7.8.5 , ( which results in 'git status' bailing with 'oops' from the
main repo )
Migrating to a newer git makes the problem vanish, as the newer git
uses info/refs for both the main repo and the submodule, and the
presence/absense of refs/heads/master is unimportant.
Solving it is reasonably straight forward on 1.7.8.5, manually extract
the SHA1 from the modules info/refs file, and inject it back into the
relevant file refs/heads/master , and things return to normal.
--
Kent
perl -e "print substr( \"edrgmaM SPA NOcomil.ic\\@tfrken\", \$_ * 3,
3 ) for ( 9,8,0,7,1,6,5,4,3,2 );"
http://kent-fredric.fox.geek.nz
prev parent reply other threads:[~2012-04-18 21:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAATnKFCAAwJYTx42iX5ZQ5-HrygFwUCWnKDNj0GDydwPYs-Nvg@mail.gmail.com>
2012-04-18 19:56 ` IRC discussion re: submodules & missing refs/heads/master Kent Fredric
2012-04-18 21:14 ` Heiko Voigt
2012-04-18 21:22 ` Kent Fredric [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAATnKFCoE6XXTB48Mvq-ay-j-1gyxxPBUvLM+REFWHLCsrTsVQ@mail.gmail.com \
--to=kentfredric@gmail.com \
--cc=git@vger.kernel.org \
--cc=hvoigt@hvoigt.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).