问题描述
我使用GIT控制生产中的应用程序的当前版本。现在我必须开始实施该应用程序的全新版本。它与目前没有任何共同之处。新的一天将会成为有一天的主人。同时，当前的版本将得到维护和发展。
你如何用Git来管理？我不喜欢创建版本2分支的想法。因为我认为（纠正我，如果我错了），这应该是标记相关。
我可以创建一个新的GIT回购，但这听起来像一个矫枉过正，毕竟它会让同一个应用程序有两个GIT回购令人困惑。
我在考虑分叉，但分叉建议从现有的开始
在这里最好的做法是在同一个仓库中创建一个新分支，与当前源无关。这样你从一个空白目录开始，但保持在同一个存储库中。此功能称为孤立分支，了解如何使用它。
I have a current version of an application in production that I control with GIT. Now I must start implementing a completely new version of that application. It will have no sources at all in common with the current one. And that new one will become the "master" one day.
in the meanwhile the current version is maintained and evolves.
How do you manage that with Git? I don't like the idea of creating a "version2" branch. because I think (correct me if I'm wrong) that this should be tag related.
I could create a new GIT repo, but that sounds to me as an overkill, and after all it will be confusing having two GIT repos for the same app.
I was thinking about forking, but forking suggest "starting from the existing"
What might be best here would be to create a new branch in the same repo, that has no relation with current sources. This way you start with a blank directory, but stay in the same repository. This feature is called "orphan branch", check this post to see how to use it.
这篇关于git练习：完成应用程序的新版本的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！