cvsimport: setup indexes correctly for ancestors and incremental imports
authorMartin Langhoff <martin@catalyst.net.nz>
Sat, 24 Jun 2006 11:13:08 +0000 (23:13 +1200)
committerJunio C Hamano <junkio@cox.net>
Sat, 24 Jun 2006 12:30:06 +0000 (05:30 -0700)
commit7ccd9009ac1fb4764ddf47a1a924ea917ff9468a
treeddb8fd251caa0eb310cf230e9d9d6d36d280cc43
parentacb70149bc5e9b9d99631a0cb59e7c2f80e92ddd
cvsimport: setup indexes correctly for ancestors and incremental imports

Two bugs had slipped in the "keep one index per branch during import"
patch. Both incremental imports and new branches would see an
empty tree for their initial commit. Now we cover all the relevant
cases, checking whether we actually need to setup the index before
preparing the actual commit, and doing it.

Signed-off-by: Martin Langhoff <martin@catalyst.net.nz>
Signed-off-by: Junio C Hamano <junkio@cox.net>
git-cvsimport.perl [changed mode: 0644->0755]