Oh, and I pushed the release button a few times, so when the visit merge is
done we'll have to adjust the version numbers being applied.
> If not then I'll merge and then troubleshoot. I think when we tell it
>not to squash the commits, it brings in your entire commit history
>followed by a merge commit.
Ok, I went ahead and tried it. It did exactly that. The commits that make
up the merge are written to the log
F*g hell. I had to restore from a backup this afternoon because my
database
bit the dust.
Looks like it's time to accelerate the replacement of Berkeley DB.
ctdldump/ctdlload is functionally complete, and we can start testing it.
I'm also thinking that maybe we want to split
