IO utilization (seeks, bandwidth, extent to which things can be cached by giving the server a lot of memory, etc.).But that can be done later.Įstimating the server resources would be needed to figure out where we would host a. If we actually needed to reference the information, we'd need to write tools. A post-receive script to write changed refs with pusher/time into $GIT_DIR/gnome_pushlog has been implemented.Use a post-push hook to log the ssh account, the refs that got updated and to what.Olav suggests 'hg pushlog' as a comparison.īeyond that tools to retrieve the information and figure out who pushed (was the first to push) a particular commit would be nice, but as long as we *could* write them, probably not immediately necessary. (The commit ID for each pushed head or whatever.) This would presumably be a look-aside log that recorded the ssh user ID for each push along with identifying information for the push.
#BEYOND COMPARE SVN CODE#
Olav considers it necessary to be able to track reliably and unforgeably who introduced code into the repository. TODO: do we really need to compare the "blame" output?
After a repository is converted, compare the final heads.What procedures do we follow to verify the integrity of the converted repositories? Does 'svn blame' output reasonably match the new ' blame'? Of course, none of 'git blame' 'git blame -M' or 'git blame -C' exactly match 'svn blame', so there's some work to figure out the appropriate metric. Do such branches migrate reasonably? Is history correct when migrated?īlame accuracy. Apparently in some cases people have done things like 'svn rm trunk svn mv branches/development trunk'. Do checkouts match byte-per-byte between the svn repository and the converted repository? With cvs => svn conversion we had some issues where images were corrupted because of different newline handling in cvs and svn. Issues that he was worried about included: One of the primary concerns that Olav (justifiably) has is making sure that the conversion proceeds accurately and we don't find problems after the fact when they are going to be hard to fix up.
Scripts and goodies for the conversion are at git clone can also see the cgit view of that repository. Working scratch-repositories and notification
0 kommentar(er)
