A few good tips, yes. For commits I use similar conventions. The key point is consistency. I like to summarize what I did in the first line, then highlight what I changed in classes and methods/functions, if significant (i.e. "knowing it could help in the future").
Of course, in Git all the changes are already easily visible (especially with a nice GUI like SmartGit/Hg), but a little English (or whatever "natural" language) can help... a couple weeks later  ;) .

Summary/title

More details  if necessary

* Class1 : what I did
- method1() : what I did (very briefly)
- method2() : what I did

*Class2 : ...
- method3() :

etc.

I could export in various formats -- CSV, TSV, XML...

In some cases,  I'd have to reformat some of the data to be able to import it. A Simple text "clip separator" as rjbull suggests would then do the job. (Either applied semi-automatically with a regex, in a text editor, or using a common search & replace function, or even by manually pasting the separator in between notes/clips -- this would certainly be quicker than to manually select and copy.)

BTW, mouser, CH&S is again my Clipboard Manager of choice. I left it behind for a while -- when it couldn't clip images -- and I decided to try it again. I'm impressed. It's a great app that does what it's supposed to do very well and has all the options I need, and more.  :-* :Thmbsup: