I'm entirely ignorant of bzr, but I've got to say that this surprises me. We use svn, which certainly works well with patch.
To the extent that svn works with patch, so does bzr, and so does git.
What I'm talking about is lossless integration with entire patch sets in the form that git does it with format-patch, send-email and am.
At this stage, isn't a "bzr vs. git vs. hg" question at all. It's just "look, it's a patch".
I think this ease and ability to work losslessly with plain text patches gives git a clear advantage over bzr.
This functionality makes it really easy for people who don't know git to interoperate with people who know it.
Lossless interoperability with plain text is a key Unix principle (see TAOUP) and something that bzr lacks.
With bzr, everybody involved with a project must use bzr. OTOH, a project that uses git can work more easily with a whole spectrum of people since sending a simple patch to a mailing list provides exactly the same ease of workflow to git-using developers as a complex multi-stage set of changes that is heavily reviewed and modified before being committed.
(I don't know hg well enough to understand how it fits in here)