On Mon, Mar 19, 2007 at 11:30:24PM -0400, Pavel Roskin wrote: > Hello! > > I don't know where this problem appeared, but it present in the current > git (1.5.1-rc1). Empty files become invalid objects in the repository: > > $ touch file > $ git-init > Initialized empty Git repository in .git/ > $ git-add file > $ git-commit -m "first commit" > Created initial commit 16a476808d3cb0a4758997ba58193a9dcfad0fd8 > error: garbage at end of loose object > 'e69de29bb2d1d6434b8b29ae775ad8c2e48c5391' > 0 files changed, 0 insertions(+), 0 deletions(-) > create mode 100644 file > $ I get the following after the last command: Created initial commit a0e02efbe85ee1c1f4b8ba703ccae2f4e64e6ed0 0 files changed, 0 insertions(+), 0 deletions(-) create mode 100644 file I use git version 1.5.1.rc1.595.gd1206 on a current gentoo system (Portage 2.1.2.2 (default-linux/amd64/2006.1/desktop, gcc-4.1.2, glibc-2.5-r1, 2.6.20-gentoo-r3 x86_64)) with a not so current portage tree (Timestamp of tree: Sat, 17 Mar 2007 12:00:01 +0000). in a few hours, i can test that on ppc32 arch, too, if you like. Regards, Nicolas Vilz - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html