Rename handling

Hi,

I've read the FAQ and Linus' philosophy on this topic, and have some questions still. I'm considering using Git and its philosophy on renames is troubling me.

My use for version control presently has most changes being written and committed by me directly, with occasional patches coming in from random others. As such, running something like 'git mv' when a rename occurs is not a problem.

My main concerns with Git are:

1) git log does not show complete history of files that have been
   renamed or copied.

   If I have foo.txt, and rename it to bar.txt, the liberal use of -M
   can tease out a proper patch from a number of places.  But
   git log bar.txt, with any set of options I can possibly come up with,
   absolutely refuses to show me the history of bar.txt before it was
   renamed to bar.txt.  git log foo.txt also does not show me the old
   history for the file.

2) For me, a rename is a logical change to the source tree that I want
   to be recorded with absolute certainty, not guessed about later.
   Sometimes I may make API changes and it is useful to see how module
   names changed, with complete precision, later.  I do not want to be
   victim to an incorrect guess, which could be possible.

Is there any way to resolve this with Git, or do I basically have to stick with Mercurial here?

-- John