| #!/usr/bin/env python | |
| """ | |
| Chuck this in : ~/bin/wineprefix | |
| $ chmod +x ~/bin/wineprefix | |
| $ wineprefix list | |
| # makes a list of directories at ~/.local/share/wineprefixes | |
| borderlands2 | |
| masseffect3 | |
| fonv |
| Copyright (c) 2015 - Xavier Cambar <@ xcambar_gmail.com> | |
| Permission is hereby granted, free of charge, to any person obtaining a copy | |
| of this software and associated documentation files (the "Software"), to deal | |
| in the Software without restriction, including without limitation the rights | |
| to use, copy, modify, merge, publish, distribute, sublicense, and/or sell | |
| copies of the Software, and to permit persons to whom the Software is | |
| furnished to do so, subject to the following conditions: | |
| The above copyright notice and this permission notice shall be included in |
Locate the section for your github remote in the .git/config file. It looks like this:
[remote "origin"]
fetch = +refs/heads/*:refs/remotes/origin/*
url = git@github.com:joyent/node.git
Now add the line fetch = +refs/pull/*/head:refs/remotes/origin/pr/* to this section. Obviously, change the github url to match your project's URL. It ends up looking like this:
I was at Amazon for about six and a half years, and now I've been at Google for that long. One thing that struck me immediately about the two companies -- an impression that has been reinforced almost daily -- is that Amazon does everything wrong, and Google does everything right. Sure, it's a sweeping generalization, but a surprisingly accurate one. It's pretty crazy. There are probably a hundred or even two hundred different ways you can compare the two companies, and Google is superior in all but three of them, if I recall correctly. I actually did a spreadsheet at one point but Legal wouldn't let me show it to anyone, even though recruiting loved it.
I mean, just to give you a very brief taste: Amazon's recruiting process is fundamentally flawed by having teams hire for themselves, so their hiring bar is incredibly inconsistent across teams, despite various efforts they've made to level it out. And their operations are a mess; they don't real
| def _get_notes(prev_tag, next_tag): | |
| with hide('stdout'): | |
| commits = run("git log --graph --pretty=format:'%h - %s (%cr by %an)%d' " | |
| + "--abbrev-commit --date=relative"+ " %s..%s" | |
| % (prev_tag, next_tag)).splitlines() | |
| commits.pop() # prev_tag went out with the previous release notes. | |
| commits.reverse() # order going down with time | |
| commits = "\n".join(commits) | |
| commits = re.sub(r"\\",r"__SUB__", commits) | |
| commits = re.sub(r"/",r"\\", commits) |