546 karma · joined January 30, 2013
I think they were just looking for a scapegoat in that particular case.
[1]: https://lists.debian.org/debian-cloud/2014/02/threads.html
As a personal google mail user I use offlineimap to synchronise with a local maildir for both redundancy and reading my emails.
-bash: sudo make me a sandwich: command not foundThis article makes one valid use of "me and X":
> in an effort to score extra points with me and Carl.
If you changed that to "Carl and I" then took out Carl it would be "to score extra points with I", which is disturbing and wrong.
I would suggest adding a "$/#" bubble which adds "\$" to the PS1 string.
If it isn't configured then netsec doesn't want split horizon. There is likely a company policy that if you are attached to their network, you are only attached to their network.
"Oh sure I've got an SD card you can borrow..."
No, this echochamber has been forced to take the red pill. "Society in general" most definitely has not, if you take 'general' to mean 'majority'.
It's nice, but has one major drawback which may be a showstopper, depending on your use case. It can only keep one version of a package at a time in each distribution.
Even worse, the domain used varies based on your card issuer so there's no consistency.
I'm sad that so few people seem to build native OS packages for deployments. My build system creates a release package and sticks it in an apt repo, then puppet installs latest version of package when it runs.
If you right click and say 'copy link' you'll get the t.co URL, but if you select the partially rendered URL and ^C you get the full (non-shortened) URL in your clipboard.
This morning a routine email was accidentally sent to many of our GitHub Enterprise customers. In these errant emails, customer email addresses were included in the To: field, making them visible to anyone who received the message.
We have stopped the remaining messages in the email batch from being sent, and are investigating how this happened.
We are very sorry that your email address was accidentally shared. Your GitHub Enterprise installation is unaffected, and no license keys or any other data were exposed during this incident.
We are investigating the root cause of this email issue and will update our blog with our findings.
Again, we are very sorry this happened. Your privacy is very important to us and we will be making changes to ensure that this does not happen again.
If you have any further questions please email us at support@github.comIt feels kind of like the wrong variable was used for To when looping through generating the day's license expiration emails.