Remove log message for 10.8 CFAllocator patching.

base/process_util_mac.mm

Index: base/process_util_mac.mm
diff --git a/base/process_util_mac.mm b/base/process_util_mac.mm
index 1ac30fe55812560ced7db63a45e0aab6825af8e1..df539df21a42326dd77f98fc89aaf5d13ed6f614 100644
--- a/base/process_util_mac.mm
+++ b/base/process_util_mac.mm
@@ -770,14 +770,6 @@ void oom_killer_new() {
 // === Core Foundation CFAllocators ===
 
 bool CanGetContextForCFAllocator() {
-  // TODO(avi): remove at final release; http://crbug.com/117476
-  if (base::mac::IsOSMountainLion()) {
-    NSLog(@"Unsure about the internals of CFAllocator but going to patch them "
-           "anyway. If there is a crash inside of CFAllocatorAllocate, please "
-           "report it at http://crbug.com/117476 . If there is a crash and it "
-           "is NOT inside of CFAllocatorAllocate, it is NOT RELATED. DO NOT "
-           "REPORT IT THERE but rather FILE A NEW BUG.");
-  }
   return !base::mac::
       IsOSDangerouslyLaterThanMountainLionForUseByCFAllocatorReplacement();

[Mark Mentovai, 2012/08/07 16:43:03]

We’re gonna need to remember to do something with this each time there’s a new
major OS version. How do you plan to track that?

[Avi (use Gerrit), 2012/08/07 16:54:54]

I plan on doing all of the same work; digging up the new structure, updating
base::mac, etc, etc. I just don't want to log "hey we're patching it anyway"
since that accomplishes nothing.

Note the length of this comment as opposed to the one from 10.7. This is thrice
the length trying to explain to people when to file bugs and where. It's clear
that doesn't work.

 }