The Normans: From Raiders to Kings by Lars Brownworth

The Normans: From Raiders to Kings by Lars Brownworth My rating: 4 of 5 stars I didn’t really know what to expect from this book. I thought the topic of the Normans was interesting but didn’t get my hopes up high since I had never heard of the author before, popular history books are usually not my taste and the cover was somewhat attention-seeking. I very quickly got drawn into the book deeply, though. Brownworth definitely succeeds in explaining the main Norman rulers and their feats. I was a bit worried about all the names and references but most of the time, a chapter or a few later, Brownworth picks up and expands on the subject he mentioned before and one gets an excellent overview. Sometimes, the chapters are a bit short and there would likely be more to say about the respective protagonist (e. g. Frederick II deserves more attention than he gets here, I think) but all in all, this book makes a very interesting read. I like how Brownworth isn’t shy to voice his own opinion about the respective protagonist at the end of almost every chapter – I don’t always agree with his assessment but I…

Re-testing patches in Gerrit with Jenkins
Exherbo / March 5, 2014

A recent request concerned the possibility to re-test patches patches in Gerrit with Jenkins. I’ve now added a very simple switch for that: In any given given change (but your own!), you can add a comment with “+1 Retest” set as a “verdict”. On the old change screen (really, change to the new one, it’s much nicer), it looks like this:   On the new change screen, it looks like this: It’s really, truly easy. You can even do it multiple time – just uncheck the “Retest” checkbox (new screen) or set “0 Retest” (old screen) first and then set it again. This works for any change as long as you are a registered user – any change but your own. Unfortunately, the Jenkins’ Gerrit-Trigger plugin simply ignores the “CommentAdded” event completely for ones own changes. If you want those re-tested, just amend your commit (no need to actually change anything; the commit timestamp will be updated) and Jenkins will see the patch’s new revision and re-run the test.   On a side note, I’d like to apologise for the instability for about 1,5 days earlier this week. There were some really nasty hardware/software issue that I had to sort out. This is…