2007-06-21 14:21 AEST by Arthur Barrett - history command should use audit database HistoryLog table

Depends on bug5004.

2016-08-08 11:33 AEST by Arthur Barrett - To facilitate this there should be a way to 'import' an existing CVSROOT/History 'file' to the audit 
database.

Note: on windows the wizard (server) could offer this as an option.

2016-08-08 11:37 AEST by Arthur Barrett - Note: import history into audit:

It would need to ensure it doesn't create duplicates.

It would need to 'delete' the history file at the end (optional?)

Maybe the server using the 'audit db' for history should be 'optional' so you can either use the 'file' 
or use the audit database e.g.:

- use audit db (recommended)
- use audit db but also write to history file
- use history file but also write to audit db
- use history file, do not write to audit db