If you make a patch for one version it may or may not improve/be applicable to another version. The bug may already be fixed or the functionality addressed already removed. At the very least some effort will be needed to integrate the changes.
That said I think your best bet is to go with cloning their git repo on an intranet server. Then you can create a branch from the stable tag (say our_stable_branch). Your devs will be able to clone this intranet repo and push whatever changes they make into our_stable_branch. Then when you want to you can merge the changes into master and push them to the main apache hive repo.
发布评论
评论（1）
如果您为一个版本制作补丁，它可能会或可能不会改进/适用于另一版本。该错误可能已被修复或已解决的功能已被删除。至少需要付出一些努力来整合这些变化。
也就是说，我认为最好的选择是在 Intranet 服务器上克隆他们的 git 存储库。然后，您可以从 stable 标记创建分支（例如
our_stable_branch）。您的开发人员将能够克隆此 Intranet 存储库，并将他们所做的任何更改推送到our_stable_branch中。然后，当您需要时，您可以将更改合并到 master 中并将它们推送到主 apache hive 存储库。If you make a patch for one version it may or may not improve/be applicable to another version. The bug may already be fixed or the functionality addressed already removed. At the very least some effort will be needed to integrate the changes.
That said I think your best bet is to go with cloning their git repo on an intranet server. Then you can create a branch from the stable tag (say
our_stable_branch). Your devs will be able to clone this intranet repo and push whatever changes they make intoour_stable_branch. Then when you want to you can merge the changes into master and push them to the main apache hive repo.