I think the old one is preferred if I want to parse Startup time from log file, not caring whether or not the log file tracks timestamp.

PS: I think the timestamp format itself is a little bit redundant. Taking a significant fraction of the log file size.

@csyangchen if one is wanting to parse start up times from the log file with timestamps turned on, one wouldn't use the startup time line anyway, but the first line with "Bitcoin version", or the line after "Default data directory". The "startup time" line is entirely redundant with timestamps enabled.

@rebroad I agree with the point you made. However, a redundant line in debug won't hurt, just not worthy of a separate pull, IMO.

Previously (appeared at least in v0.6.0, fixed by now ) there is a duplicated timestamp output in main.cpp, on the recv message: "timestamp timestamp received: ...". That, I think, is a duplication worthy of fix, considering frequency of the recv message.

If we actually want a start time message, I think we should also provide a stop time message, so that users can parse the debug file and calculate the session time, when timestamp is not provided.

@csyangchen The duplicate timestamps are fixed, I created a patch for this a few weeks ago. I also think this pull is unneeded.

It's not duplicate if you have logtimestamps disabled. Just because someone might be interested in a few cases where times matter, doesn't mean they want every line timestamped.

@rebroad , did you test this at all? It doesn't compile... -.-

@luke-jr everything takes so long to compile on my laptop, as due to the way git works, it causes all file modification times to be changed, so make tried to recompile everything. If I could work out a way for make to use checksums instead of modification times, then my compiles wouldn't take so long, and I'd have tested this. thanks for the fix!

I still think this one is no needed, your other current pulls that re-work debug-messages and stuff make far more sense.

ACK, for ever-so-slightly enhanced privacy

Automatic sanity-testing: FAILED MERGE, see http://jenkins.bluematt.me/pull-tester/8617052cb72f4ac96ce5f8dbf024d7cbf41f0351 for test log.

This pull does not merge cleanly onto current master