Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

base 커밋 관리 방안. #16

Closed
pismute opened this issue Mar 9, 2015 · 1 comment
Closed

base 커밋 관리 방안. #16

pismute opened this issue Mar 9, 2015 · 1 comment

Comments

@pismute
Copy link
Member

pismute commented Mar 9, 2015

지금은 각 챕터별로 하고 있지만, 정리가 되면 어떻게 관리하는게 좋을지 고민했었는데, 아이디어가 하나 떠올라서 남깁니다.

  1. base 브랜치를 만든다: progit/progit2@master를 추적하는 브랜치를 만들어 놓는다. progit2는 progit2-ko와 전화 다른 프로젝트이므로 basemaster 사이의 base 커밋은 없는 상태로 관리. 의미 없이 저장소 크기가 증가되지만 편할 것 같습니다.

@lethee, @lnyarl

@pismute
Copy link
Member Author

pismute commented Apr 23, 2015

#21 참고

@pismute pismute closed this as completed Apr 23, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant