Re: Problems with unrecognized headers in git bundles
- From
Øyvind A. Holm <sunny@sunbase.org>
- Date
- Feb 22, 2012, 20:40 UTC
- Message-ID
- <CAA787r=J_GVcusCXQHsu4Tc=k=oc=NZ9JE0x4JaOdn61wLijbg@mail.gmail.com>
- In-Reply-To
- <CAA787rm4c1zYgQJ3kP5=ujpEK1Dda9+h_P3BBmg2yX2eZca=TA@mail.gmail.com>
On 22 February 2012 21:25, Øyvind A. Holm <sunny@sunbase.org> wrote:
Show 15 quoted lines
> On 22 February 2012 17:05, Jannis Pohlmann wrote: > > creating bundles from some repositories seems to lead to bundles > > with incorrectly formatted headers, at least with git >= 1.7.2. When > > cloning from such bundles, git prints the following error/warning: > > > > $ git clone perl-clone.bundle perl-clone > > Cloning into 'perl-clone'... > > warning: unrecognized header: --work around mangled archname on... > > Have researched this a bit, and I've found that all git versions back > to when git-bundle was introduced (around v1.5.4) produces the same > invalid line. The culprit is commit > 3e8148feadabd0d0b1869fcc4d218a6475a5b0bc in perl.git, branch > 'maint-5.005'. The log message of that commit contains email headers, > maybe that's the reason git bundle gets confused?
...or maybe because the log message doesn't contain any empty lines, so they're joined together into an insanely long line. I've seen this behaviour before, in git-am or git-apply, I think. Anyway, when the bundle doesn't contain this commit, the line is not present.
Øyvind