Correspondence of the Family of Hatton: Being Chiefly Letters Addressed to Christopher, First Viscount Hatton, 1601-1704 - Vol. 1

Correspondence of the Family of Hatton: Being Chiefly Letters Addressed to Christopher, First Viscount Hatton, 1601-1704 - Vol. 1

Read FREE!

Correspondence of the Family of Hatton: Being Chiefly Letters Addressed to Christopher, First Viscount Hatton, 1601-1704 - Vol. 1

Correspondence of the Family of Hatton: Being Chiefly Letters Addressed to Christopher, First Viscount Hatton, 1601-1704 - Vol. 1

Read FREE!

Excerpt

The letters which are printed in these volumes have been selected from the correspondence of the family of Hatton which forms part of the Hatton-Finch papers preserved in the British Museum. These papers, contained in forty-nine volumes, comprise -- as their title indicates -- the general correspondence and papers of the connected families of Hatton, Viscounts Hatton, and Finch, Earls of Nottingham and Winchilsea. They extend over the years 1514-1779; but the larger portion concerns the Hattons, and of those which relate to the Finches the greater number are political papers of the second Earl of Nottingham. The collection was purchased by the Trustees of the British Museum in 1874, and now bears the numbers, Additional MSS. 29,548-29,596.

That branch of the family of Hatton with which we have to do was descended from John Hatton, a younger brother of William, the father of Sir Christopher Hatton, Queen Elizabeth's Lord Chancellor. John Hatton had a son of the same name, of Long Stanton, co. Cambridge, who became the father of Sir Christopher Hatton of Kirby, the writer of the first of our letters. Sir Christopher, who was a Knight of the Bath, became heir to the estate of his namesake, the Lord Chancellor, on the death of his cousin, Sir William Newport-Hatton, and, dying in 1619, was succeeded . . .

Search by... Author
Show... All Results Primary Sources Peer-reviewed

Oops!

An unknown error has occurred. Please click the button below to reload the page. If the problem persists, please try again in a little while.