rtomayko

8 ms·

31.
by rtomayko 15y ago
(I work at GitHub.) Linus wrote into github support with some good and pointed feedback as well, most of which was related to email sent when a pull request is opened vs. what you might expect to see when someone submits a patch series to a
32.
by rtomayko 15y ago
I don't think we have any strict non-drinkers but there's definitely some lightweights ( cough Holman cough ) so I think he'd be fine. ;)
33.
by rtomayko 15y ago
Just wanted to note that a fork is automatically created and a pull request created when you edit a file in a repository you don't have push access to. So the workflow is even simpler: 1.) see file, 2.) edit file and save, 3.) land on send
34.
Designing GitHub for Mac(warpspire.com)
360 points by rtomayko 15y ago|76 comments
35.
by rtomayko 15y ago
As a first measure I think we could make it so that once you removed yourself as a collaborator from a project, it would not be possible for the person to re-add you. I realize that's not ideal but would be much more trivial to implement th
36.
by rtomayko 15y ago
I'm the GitHub employee that fixed the bug. I usually try not to get involved with stuff like this but I feel like I'm in a unique situation to correct the record here. "They purposefully allow this glaringly obvious mechanism for insultin
37.
by rtomayko 15y ago
There's a list of short aliases enabled in git-sh by default here: http://rtomayko.github.com/git-sh/
38.
by rtomayko 15y ago
Best case you have to do three RTs for a full SSL handshake (without false start anyway), so a RTT of 300ms will bring you pretty close to that 1000ms. We (github.com) certainly have average 1000ms SSL handshakes in Asia -- we're 5 RTs for
39.
by rtomayko 15y ago
FWIW, I was copied on an email exchange with Brian Kernighan regarding the piece and he referred to AWK as "Awk". Thought you'd like to know :)
40.
by rtomayko 15y ago
GNU's is "Awk" but the language and most early implementations are referred to as "AWK" from everything I've read. More here: http://en.wikipedia.org/wiki/AWK
41.
by rtomayko 15y ago
Me too :) Actually, check out the talk mentioned at the beginning of the essay. Pretty sure I build that exact pipeline at some point near the middle.
42.
by rtomayko 15y ago
Updated. Thanks!
43.
by rtomayko 15y ago
It's not. The primary profile email is used currently: https://img.skitch.com/20110426-gjj8fcrdmayyinfgb57bgtgcns.j... That's an interesting request though. This isn't the email I have configured in my ~/.gitconfig either.
44.
by rtomayko 15y ago
Well said. When I talk to people at conferences and whatnot about GitHub, they're often surprised we run a core git stack with few modifications. Repositories are stored as plain old git repositories and we use git's normal command line int
45.
The Shell Hater's Handbook(confreaks.net)
1 points by rtomayko 15y ago|0 comments
46.
by rtomayko 16y ago
omg please turn development mode off antirez. Are you trolling me?
47.
by rtomayko 16y ago
On github.com, many types of requests can result in one or more calls to git commands. Every ms we can shave there can have a pretty big impact on response time.
48.
by rtomayko 16y ago
Can you dump some ping times? 2-4s is waaaay outside of what I'd expect the average response time to be.
49.
by rtomayko 16y ago
"Bare metal" as in "not-a-VM", yeah.
50.
by rtomayko 16y ago
Where are you located (geographically)? We have a couple developers more or less dedicated to performance at this point, and we're moderately satisfied with server response time for most areas of the site (the issue tracker is a notable exc
51.
by rtomayko 16y ago
Same :)
52.
by rtomayko 16y ago
They're not.
53.
by rtomayko 16y ago
Here's a few review threads in the wild to illustrate: https://github.com/legalbox/lb_js_scalableApp/pull/1 https://github.com/jnicklas/capybara/pull/271 https://github.com/gem/openquake/pull/25 EDIT: formatting.
54.
by rtomayko 16y ago
Yeah, exactly. We (GitHub) use reflogs on the server, so everything that was pushed was in the repository and can't be gc'd out for at least 90 days. The master branch ref was just pointing at the wrong commit due to the forced pushes.
55.
by rtomayko 16y ago
Yeah. It's definitely not a heroku issue. We were configured to run on a single backend. It's since been increased and should be better now.
56.
by rtomayko 16y ago
Okay. The session cookie is marked secure and is sent only in response to HTTPS requests. That should cover everything.
57.
by rtomayko 16y ago
We fat fingered the config. The cookie is marked secure now but we found another issue where it's being sent back on redirected HTTP requests. It should be all plugged up in a bit.
58.
by rtomayko 16y ago
I have a great way of dealing with this that's simple, fun, and requires very little lead time: get drunk. I head out around 10PM and drink beer or whisky repeatedly until I'm completely intoxicated. By 2AM or so all I want to do is go to s
59.
by rtomayko 16y ago
That's fucking ridiculous and the stupidest thing I've ever heard of in my life.
60.
by rtomayko 16y ago
Except none of that stuff was indexed by google at time of writing. The links that were added to Wikipedia after the article was published made your search possible: http://en.wikipedia.org/wiki/Talk:Hyperlink#what_does_href_s... Trust me

More ›