Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "LTS/HowTos"
< LTS
| Line 9: | Line 9: | ||
= Known Issues = | = Known Issues = | ||
| + | |||
| + | == Fail to clone submodules using msysgit == | ||
| + | |||
| + | Per Bug 376400 we discovered that msysgit has a max character limit somewhere around 256 which causes cloning files with a path longer than that to fail. | ||
| + | |||
| + | See: https://bugs.eclipse.org/bugs/show_bug.cgi?id=376400#c4 | ||
== Cannot git clone via ssh:// protocol (Resolved) == | == Cannot git clone via ssh:// protocol (Resolved) == | ||
The issue with this is that most user accounts on the Forge will not have shell access to the forge and the ssh:// protocol requires shell to operate. The solution we decided to go with was we provisioned a https:// protocal instead which we will recommend users to use instead.<br> | The issue with this is that most user accounts on the Forge will not have shell access to the forge and the ssh:// protocol requires shell to operate. The solution we decided to go with was we provisioned a https:// protocal instead which we will recommend users to use instead.<br> | ||
Revision as of 09:41, 6 November 2012
Contents
Howtos
Using TortoiseGit to "git submodule update"
- Navigate to your git repository which you cloned (eg. eclipse.platform.releng.aggregator)
- Right click > TortoiseGit > Submodule Update
- Select to Initialize Submodules
- Click OK
Known Issues
Fail to clone submodules using msysgit
Per Bug 376400 we discovered that msysgit has a max character limit somewhere around 256 which causes cloning files with a path longer than that to fail.
See: https://bugs.eclipse.org/bugs/show_bug.cgi?id=376400#c4
Cannot git clone via ssh:// protocol (Resolved)
The issue with this is that most user accounts on the Forge will not have shell access to the forge and the ssh:// protocol requires shell to operate. The solution we decided to go with was we provisioned a https:// protocal instead which we will recommend users to use instead.