git-cvsimport bug

Emanuele Giaquinta· Nov 27, 2007, 15:01 UTC · lore

Hi,

a call to git-cvsimport after a 'git-pack-refs --all' seems to mess up the origin branch, because the first new change is committed with no parent (git-cvsimport reports 'Parent ID (empty)'). It does not happen if I disable loose refs pruning with --no-prune. A tiny test repo you can use to reproduce the problem is mextli.tomaw.net/~exg/lzf.tar. Is it expected?

Thanks,

Emanuele Giaquinta

Jeff King· Nov 28, 2007, 16:57 UTC · re: Emanuele Giaquinta · lore

Re: git-cvsimport bug

On Tue, Nov 27, 2007 at 04:01:36PM +0100, Emanuele Giaquinta wrote:

Show 6 quoted lines

> a call to git-cvsimport after a 'git-pack-refs --all' seems to mess up
> the origin branch, because the first new change is committed with no
> parent (git-cvsimport reports 'Parent ID (empty)').
> It does not happen if I disable loose refs pruning with --no-prune. A
> tiny test repo you can use to reproduce the problem is
> mextli.tomaw.net/~exg/lzf.tar. Is it expected?

Some of git-cvsimport is quite old, and it accesses the ref files directly. It should be fairly easy to fix; I will post a patch in a few minutes.

-Peff