WireGuard on pfSense

Netgate has “just” published their first blog post, describing official WireGuard support in the latest development snapshot of pfSense 2.5.0. As a network engineer, routing enthusiast, technical supporter, and DN42 participant. Hearing about the upcoming WireGuard support for pfSense has me very excited due to the ease of use. And simplistic configuration. Making it – … Read more

Git committer e-mail. Which t use ?

Podcast (7 October 2015) http://bikeshed.fm/35


“Do you use a private or work e-mail when pushing git commits to repositories.”

???

The question is worth asking yourself as it’s (also) ’bout attribution of work you have done in either a public (fx GitHub) or private (fx Internal) domain.

The use of .mailmap partially solves the issue if you have by accident used multiple e-mail addresses when pushing commits in the past. But┬áconsider your opinion going forward…

“Do you stick with using one single e-mail of your own or the company provided one.”

???


Looking back myself I will probably (!) stick with using my own mail address for all git commits I do in the future. As attribution back to me becomes easier and the knack of using .mailmap will be (mostly) a thing of the past! (plus gitlab community edition does not yet support the .mailmap functionality!)