-
Notifications
You must be signed in to change notification settings - Fork 78
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
separate docs subdirectory #125
Comments
I will do this, but need to figure out which git method to use for the subpackage... SEACAS is used in a few other places and they each use a different subpackage method, so I need to see how best to do this and not break their uses... |
Good to hear! Yes, this can be a tricky decision. I've seen several drawbacks to using git submodules (one of the possible methods). In my opinion the lowest risk is to not associate them at all using git, simply have sufficient advertisement (README, etc) that users know where to find the docs repository without git's help. |
Stale issue message |
This has been done. Docs are now in |
It would greatly speed up clone times of this repository if the docs subdirectory were moved into a separate Git repository, and its history removed from this one.
The text was updated successfully, but these errors were encountered: