2. Never merged, though a similar patch by the same person was merged a couple of weeks later. Try, try, again.
3. Never merged. Waiting on Bram.
4. Merged after 6 months, only because users constantly pestered. This patch was 12 lines, all straightforward.
5. Never merged. Bram said it was on his to-merge list in 2013.
All of these patches are pretty small. It shouldn't take long to reply with "Yes", "No", or "fix this". Yet the response is often one reply, followed by crickets. As 2 and 5 show, even the "yes" patches can fall through the cracks.
Bram's initial response can be quick, but it's often an ordeal to actually get a patch merged, even for trivial ones. This is likely due to a combination of Bram being a very busy person and mailing lists being terrible for this sort of thing.
So I don't think you can look for his response in the mailing list for a submission if it was merged or not. You have to look at the stream of merged patches.
Also it looks like a patch that is merged is put on the mailing list at the root and not as a reply to peoples messages.
So it is hard to tell how long someone submits something and when a patch is merged by looking at responses. You would have to find a patch someone submitted, then find Brams "Patch" messages to find when it was merged and compute time difference