Comment 17 for bug 347729

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Matthew Brett wrote:
> Hi,
>
> On Wed, Feb 10, 2010 at 8:59 AM, Gabriel Filion
> <email address hidden> wrote:
>> just a small hint: could this be caused by the fact that git actually
>> doesn't store empty files in commits (thus not finding anything that
>> points to the example commits made in the first example of this bug
>> report -- touch a, bzr add a, bzr commit)?
>
> Do you mean, that bzr fastimport cannot deal with empty git commits?
> Is this a bug or a feature?
>
> Thanks a lot,
>
> Matthew
>

So if you add an empty file, which cannot be tracked in git, and commit
it, I would guess that you would get a new Commit object, but not a new
Tree object. I don't know if git would refuse a new Commit without a new
Tree, but I would think it would support importing that. (After all, you
could always be reverting back to a previous state, which is identical
as well.)

John
=:->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkty/VgACgkQJdeBCYSNAAOXAACghYSy+3Rr2B/baK/vTWfQoAH0
/1UAn12W+JUz3lBvhnRnE2HzjnjcE5JH
=szdz
-----END PGP SIGNATURE-----