Single Line 과 동일하지만, Multi Line 으로 가면 두 번째 라인은 반드시 비워둘 것
세 번째 라인부터 Change 상세를 리스트 형식으로 기술
Linear History in git
장점
git bisect
possibility of submitting with history to another version control system like SVN
Documentation for the posterity. A linear history is typically easier to follow. This is similar to how you want your code to be well structured and documented: whenever someone needs to deal with it later (code or history) it is very valuable to be able to quickly understand what is going on.
Improving code review efficiency and effectiveness. If a topic branch is divided into linear, logical steps, it is much easier to review it compared to reviewing a convoluted history or a squashed change-monolith (which can be overwhelming).
When you need to modify the history at a later time. For instance when reverting or cherry-picking a feature in whole or in part.
Scalability. Unless you strive to keep your history linear when your team grows larger (e.g. hundreds of contributors), your history can become very bloated with cross branch merges, and it can be hard for all the contributors to keep track of what is going on.
현재까지의 상태는 이럴 것이다.