projects / git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: b020dcd) | patch
SVN import: Use one log call
authorMatthias Urlichs <smurf@smurf.noris.de>
Tue, 29 Nov 2005 07:13:04 +0000 (08:13 +0100)
committerJunio C Hamano <junkio@cox.net>
Tue, 29 Nov 2005 18:51:43 +0000 (10:51 -0800)
commit034908047d8c46fb4e1323285b3b066567c7fadc
tree4000f8b8d01ad35929972c07d98d89e2280cf3d3tree | snapshot
parentb020dcd54cc3f2b783339f83d09e46bb7ff08a3ecommit | diff
SVN import: Use one log call

One "svn log" (or its equivalent) per revision adds delay and server load.
Instead, open two SVN connections -- one for the log, and one for the files.

Positive side effect: Only those log entries which actually contain data
are committed => no more empty commits.

Also, change the "-l" option to set the maximum revision to be pulled,
not the number of revisions.

Signed-off-by: Junio C Hamano <junkio@cox.net>
Documentation/git-svnimport.txt diff | blob | blame | history
git-svnimport.perl diff | blob | blame | history
Unnamed repository; edit this file 'description' to name the repository.