John of Gau nt

Correction in post: I meant to say that I went to the TREE. . . . and did not know where to start to correct it.

he is shown as king edward lll's son on king edwards tree.but- there are a lot of king edward's managers that need to read your post. or .....
we could start notifying them. no time at the moment to do that for me.

I cleaned some of this up my un-merging several obviously wrong Johns.

Unfortunately, the way Geni merging currently works, it only takes one person to add an incorrect profile to a merge stack to plant the seeds for a giant mess with scores of wrong profiles merged together. This is because the Tree matches don't just show the main profile in the stack- it considers them as still being seperate. Once a wrong one sneaks in there, then people can start merging other profiles that match THAT OTHER profile- no longer comparing to the original/main one in the stack. That's why you'll often see lots of correct profiles in a stack, and then several wrong ones in a row (that match each other, but not the main profile), followed by several more correct ones.

i notified a few of them before geni went into hyperspace......will do more later.
something like 92 matches.

I am not sure if I'm one of those that caused the confusion. If you come across my name, please know I will fix it immediately.

I am not sure if I'm one of those that caused the confusion. If you come across my name, please know I will fix it immediately.

no confusion, just duplicates of the same duke of lancaster-john gaunt. merge merge merge please.

Sorry- I have a typo in my message above. The first sentence should read: "I cleaned some of this up BY un-merging several obviously wrong Johns."

None of the pending merges were mine. But LOTS were wrong.

I have tried many times to look at his tree, but keep getting an error message.

Lynette, you should report your problem to help@geni.com.

I tried to do some merging... but some of the profiles were locked and some said "cannot merge spouse/partner." I'll try again later, too.