Edge Rewrite
// request.cf · coarse context

A page that knows where it met you.

Only coarse request metadata is shown. This demo does not display or persist visitor IP addresses.

Country
US
Cloudflare location
CMH
Connection
HTTP/2
Language
Not provided

Ray ID: a29a49b92e72724e

Jump to content

Talk:Hendrik Prinsloo

Page contents not supported in other languages.
Add topic
From Wikipedia, the free encyclopedia
Latest comment: 1 year ago by 105.245.108.128 in topic Incorrect information

Untitled

[edit]

The reason for calling the page Colonel Hendrik Frederik Prinsloo and not just Hendrik Frederik Prinsloo is to distinguish him from his father and grandfather who have the same names and whose pages are currently in preparation. Comment/advice? Whoosis (talk) 11:17, 3 January 2009 (UTC)Reply

Depends what they are notable for? Also, was this man usually known as Hendrik Prinsloo or by his full name Kernel Saunters (talk) 10:32, 6 January 2009 (UTC)Reply
It makes more sense just to call the page Hendrik Prinsloo. His father was a Boer Commandant who played a critical role in the British defeat at the Battle of Spioenkop and died at the Battle of Leliefontein. The British general at the latter battle raised funds in the UK to erect a memorial to him. The other Hendrik Prinsloo was one of 5 rebels executed by the British for the 1815 Slagter's Nek Rebellion in the Cape. The execution had a significant effect on South African history. How about the three pages being Hendrik Prinsloo, Hendrik Prinsloo (Boer leader) & Hendrik Prinsloo (Slagtersnek rebel)? Suggestions?Whoosis (talk) 14:03, 29 January 2009 (UTC)Reply

Incorrect information

[edit]

He was also a direct descendant of Hendrik Frederik Prinsloo (1784–1816), who was executed for his involvement in the Slagter's Nek rebellion in 1815.

According to our research on Wiki Tree he is a desendent of https://www.wikitree.com/wiki/Prinsloo-605 Hendrik Frederik Prinsloo (abt. 1788 - abt. 1859)

Have a great day Susan 105.245.108.128 (talk) 08:46, 8 January 2025 (UTC)Reply