일 | 월 | 화 | 수 | 목 | 금 | 토 |
---|---|---|---|---|---|---|
1 | 2 | 3 | 4 | 5 | 6 | 7 |
8 | 9 | 10 | 11 | 12 | 13 | 14 |
15 | 16 | 17 | 18 | 19 | 20 | 21 |
22 | 23 | 24 | 25 | 26 | 27 | 28 |
29 | 30 | 31 |
- cygwin
- gfortran
- Anaconda
- arXiver
- python
- hyperref
- GSL
- SSH
- vi
- LaTeX
- MAC
- mpi4py
- HFS+
- conda
- HDF5
- jupyter
- vim
- cython
- h5py
- Matplotlib
- virtual
- portforwarding
- Windows
- tab space
- intel compiler
- datascience
- polyglot
- c++
- Visual Studio
- openmp
- Today
- Total
Astro Coke
[Git] git merge between master and branches 본문
You shouldn't merge Farmcrops directly into master, because you run the risk of breaking the code in master, which, by convention, is supposed to be more stable. Instead, check out Farmcrops and merge master into it.
git checkout Farmcrops
git merge master
Then you'll get
-- o -- o -- o [master]
|
o -- o -- o [HEAD -> Farmcrops]
Run some tests; make sure everything works as expected.
Then check out master and merge Farmcrops into it:
git checkout master git merge Farmcrops
git checkout master
git merge Farmcrops
Your repo will then look like this:
-- o -- o -- o
| |
o -- o -- o [HEAD -> master,Farmcrops]
(Note that this merge is a fast forward: it doesn't create a merge commit because Farmcrops is a direct descendant of master.)
Now check out Farmcrops again and continue your experiment, make more commits on it, etc...
-- o -- o -- o
| |
o -- o -- o [master]
|
o -- o -- o [HEAD -> Farmcrops]
You can always fall back on master (which now contains "the first round of changes", as you put it) if your new experiment on Farmcrops doesn't pan out so well.
'Computer Setup' 카테고리의 다른 글
[Linux] create separate tar files from multiple folders (files) (0) | 2021.01.19 |
---|---|
[Mac] ahnlab safe transaction on Mac OSX (0) | 2020.12.18 |
[Jekyll] Dependency errors when gem bundles are updated (0) | 2020.08.21 |
[Latex] pdflatex occasionally conflicts with hyperlink breaking (0) | 2020.08.16 |
[Windows] Python setup for Sub-Users (0) | 2020.07.29 |