Comment 3 for bug 245170

We use Bazaar not only to store historical versions of project files, but also to manage a complex sync scenario involving online and offline users. Bazaar replaced our custom procedure based of a series of rsync calls, thats was working fine but very hard to manage. We found Bazaar very usefull and reliable.

But we have lost all our document history: modification time is an important file metadata and a lot of tools relies on it.
Worse, we lost the original timestamp on the initial commit: if you start using Bazaar on a new project or set of files, you can retry history information from the Bazaar metadata themself, not simple but feasible. But if you load a bazaar slot with a long history set of documents, there is no way (as I can see) to save the original timestamp of files.

BTW, a partial solution would be if we can have, at least, the last commit timestamp on each file, but this is not the case: using checkout or update, as stated, gives to all the files the same, current local computer time, that's makes no sense at all.