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

关于结构调整的建议 #413

Open
cloes opened this issue Jan 23, 2017 · 2 comments
Open

关于结构调整的建议 #413

cloes opened this issue Jan 23, 2017 · 2 comments
Assignees

Comments

@cloes
Copy link
Contributor

cloes commented Jan 23, 2017

因为三年前的翻译版本和现在的翻译版本存在章节上的差异,例如:旧版本的“分区”是第18章,而目前翻译版本的“分区”是第19章,在翻译过程中需要用git mv命令把chapter_18改为chapter_19,但是chapter_19已经存在,其他贡献者如果没有将chapter_19改为chapter_20的话,后面解决冲突会话费很大力气。

建议:管理者先对每个章节进行git mv 调整后,大家在git pull回去按照自己新的文件夹进行翻译,避免PR的时候产生的冲突。

@cloes
Copy link
Contributor Author

cloes commented Jan 23, 2017

如果不使用git mv进行改名,后面的修改会丢失前面的git历史记录

@diguage
Copy link
Contributor

diguage commented Jan 23, 2017

支持!

@TimoKitty 帮我检查一下我提交的文件名列表和最新文档中的目录是否一致吧。

这个工作量有点大, @cloes @rikki 再喊上其他几个小伙伴,我们一起分工来吧这个搞了吧。如何?

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

2 participants