While, that's true that we have a large codebase, ~500 mb code, in 100k
files, I do not think that it is hard for git to maintain them as a
whole. I think we shall not change the workflow unless we have a strong
reason to do that, and we are clear on the benefits and drawbacks of the
change.
I myself do not feel any slowness on git operations even when I kept my
code was on HDD. I've switched to SSD due to the speed up the builds
recently. So at the moment, I do not see any benefit on that change.
On 9/6/20 7:15 AM, Eric Bresie wrote:
While reading an article recently, the topic of git submodules came up, which I
started looking up the topic (1).
Given the size of the netbeans code base and the complexity of other projects
inclusion like the specific plugin/clusters, etc., I was wondering if it’s
worth considering breaking out some of these elements into separate submodule
projects.
This would reduce the overall size of the netbeans project (but the placeholder
submodule - normally empty until submodule is pulled) and would allow each
submodule to be managed independently.
The drawback may be a little learning curve on submodule usage which may add to
some issues initially as well as a few extra steps during builds.
(1) https://git-scm.com/book/en/v2/Git-Tools-Submodules
Eric Bresie
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
