Orthodox C++ (sometimes referred as C+) is minimal subset of C++ that improves C, but avoids all unnecessary things from so called Modern C++. It's exactly opposite of what Modern C++ suppose to be.
height: 600 | |
license: mit |
// Warning: Lights made with this script can not be saved! | |
var lightEffect = EffectCollection.FindEffect("Flood Light Orange") as LightEffect; | |
// Final position in prop | |
Vector3 pos = new Vector3(0f,10f,0f); | |
// this would be in the center of the prop, 10m above ground | |
// Final direction in prop | |
Vector3 dir = new Vector3(0f,1f,0f); |
If you have a package where a lot of people are still using a legacy version of it you might want to keep pushing (security-)fixes to that "branch".
Let's say the "latest" version of your package is "5.4.0", but there is as significant amount of people still using "4.7.4" – the last version you released before doing "5.0.0".
You found a critical bug in "5.4.0" and push it as out as "5.4.1", but it applies to "4.7.4" as well and so you want to do "4.7.5".
Assuming you have semantic-release already set up, you can follow these steps to get that "4.7.5" legacy support release out.
- Go to the relevant commit:
git checkout v4.7.4
- Create a new branch from it:
git checkout -b 4.x
(You can choose any branch name, just make sure to use the same in step 3)
// Run this in the F12 javascript console in chrome | |
// if a redirect happens, the page will pause | |
// this helps because chrome's network tab's | |
// "preserve log" seems to technically preserve the log | |
// but you can't actually LOOK at it... | |
// also the "replay xhr" feature does not work after reload | |
// even if you "preserve log". | |
window.addEventListener("beforeunload", function() { debugger; }, false) |
- Install cmder_mini (msysgit is already installed, so no need for full version)
- In Cmder, open settings:
Win + Alt + P
- Under Startup > Tasks, add a task called
{bash}
with the following settings:- Task parameters (set icon):
- For Cmder icon:
/icon "%CMDER_ROOT%\cmder.exe"
- For Git icon:
/icon "C:\Program Files (x86)\Git\etc\git.ico"
- For Cmder icon:
- Commands (open Git's bash shell):
- Task parameters (set icon):
"C:\Program Files (x86)\Git\bin\sh.exe" -l -new_console:d:%USERPROFILE%
# Steps we will take: | |
# 1. Change boot2docker image type (this will take long) | |
# 2. Resize image | |
# 3. Resize partion (using GParted) | |
# | |
# Also see: https://docs.docker.com/articles/b2d_volume_resize/ | |
# Stop boot2docker | |
boot2docker stop |
Branch A has commits (X,Y) that also need to be in Branch B. The cherry-pick operations should be done in the same chronological order that the commits appear in Branch A.
cherry-pick
does support a range of commits, but if you have merge commits in that range, it gets really complicated
git checkout branch-B
git cherry-pick X
git cherry-pick Y