- http://stackoverflow.com/questions/804115 (
rebase
vsmerge
). - https://www.atlassian.com/git/tutorials/merging-vs-rebasing (
rebase
vsmerge
) - https://www.atlassian.com/git/tutorials/undoing-changes/ (
reset
vscheckout
vsrevert
) - http://stackoverflow.com/questions/2221658 (HEAD^ vs HEAD~) (See
git rev-parse
) - http://stackoverflow.com/questions/292357 (
pull
vsfetch
) - http://stackoverflow.com/questions/39651 (
stash
vsbranch
) - http://stackoverflow.com/questions/8358035 (
reset
vscheckout
vsrevert
)
Discover gists
THIS WAS ORIGINALLY POSTED ON MY TUMBLR ON FEB 25, 2011. I forgot I had a Tumblr account. I recently logged in (in light of the acquisition by Automattic), found some old posts, and I'm republishing them exactly as they were with zero modifications.
Amazon announced CloudFormation to the public yesterday, and while the general opinion I could glean from various sources shows that people are excited about this new technology, many are still unsure what it is and how it fits into their current cloud workflow. I feel as though I have a firm grasp on CloudFormation and will attempt to answer some questions here.
Note: I'm definitely not a representative of Amazon in any way, and anything here is simply my educated opinion on the matter.
Some stats: - Total number of links: 23983
Short (72 chars or less) summary
More detailed explanatory text. Wrap it to 72 characters. The blank
line separating the summary from the body is critical (unless you omit
the body entirely).
Write your commit message in the imperative: "Fix bug" and not "Fixed
bug" or "Fixes bug." This convention matches up with commit messages
// SPDX-License-Identifier: MIT | |
pragma solidity 0.8.19; | |
// Deploy this contract on Fuji | |
import "@openzeppelin/contracts@4.6.0/token/ERC721/extensions/ERC721URIStorage.sol"; | |
import "@openzeppelin/contracts@4.6.0/utils/Counters.sol"; | |
import "@openzeppelin/contracts@4.6.0/utils/Base64.sol"; | |
import "@chainlink/contracts/src/v0.8/interfaces/VRFCoordinatorV2Interface.sol"; |
# Original by Daniel L. Greenwald | |
# http://dlgreenwald.weebly.com/blog/capitalizing-titles-in-bibtex | |
# Modified by Garrett Dash Nelson | |
import re | |
from titlecase import titlecase | |
# Input and output files | |
my_file = 'library.bibtex' | |
new_file = 'library-capitalized.bibtex' # in case you don't want to overwrite |
#define エスティーディー std | |
#define アイオーストリーム <iostream> | |
#define ユージング using | |
#define イフ if | |
#define インクルード #include | |
#define イント int | |
#define シーアウト cout | |
#define シーイン cin | |
#define ネームスペース namespace | |
#define ブール bool |
#!/bin/bash | |
wget https://dl.pstmn.io/download/latest/linux64 -O postman-linux-x64.tar.gz | |
sudo tar xvzf postman-linux-x64.tar.gz -C /opt | |
sudo ln -s /opt/Postman/Postman /usr/bin/postman | |
cat << EOF > ~/.local/share/applications/postman2.desktop | |
[Desktop Entry] | |
Name=Postman | |
GenericName=API Client |
-
Click on the project you want to rename in the "Project navigator" in the left panel of the Xcode window.
-
In the right panel, select the "File inspector", and the name of your project should be found under "Identity and Type". Change it to your new name.
-
When the dialog asks whether to rename or not rename the project's content items, click "Rename". Say yes to any warning about uncommitted changes.