Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "EGit/Differences to Git"
< EGit
| Line 1: | Line 1: | ||
Main differences between original (command line, C) Git and JGit (EGit). | Main differences between original (command line, C) Git and JGit (EGit). | ||
| − | *JGit does not support any SVN bridging operations | + | *JGit does not support any SVN bridging operations. There is a feature request discussed in [https://bugs.eclipse.org/bugs/show_bug.cgi?id=315264 bug 315264]. The most common ones (svn rebase, svn fetch, svn dcommit) can be handled with external launchers. |
*JGit does not support bundles in any way - they can't be created pulled, or queried. There are no current plans to add bundle support. | *JGit does not support bundles in any way - they can't be created pulled, or queried. There are no current plans to add bundle support. | ||
*JGit supports the merge strategies "resolve" and "recursive" | *JGit supports the merge strategies "resolve" and "recursive" | ||
| − | *JGit is | + | *JGit is missing support for a number of configuration settings, including most of the ones related to merging. The list of some of them: |
**'push.default' no supported. | **'push.default' no supported. | ||
*Hooks are not currently supported. | *Hooks are not currently supported. | ||
| − | *Creation of light-weight and signed tags is not supported. | + | *Creation of light-weight and signed tags is not supported ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=386908 bug 386908]). |
| − | * | + | *Creation of signed commits is not supported ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=382212 bug 382212]). |
*When a directory is deleted from the working set, EGit will immediately remove it from the working tree and stage the deletion of the files. If you want to undo this you must manually recreate the deleted directory first. At that point you can use standard egit tools to recover the deleted files. [this one might be obsolete] | *When a directory is deleted from the working set, EGit will immediately remove it from the working tree and stage the deletion of the files. If you want to undo this you must manually recreate the deleted directory first. At that point you can use standard egit tools to recover the deleted files. [this one might be obsolete] | ||
| − | |||
| − | |||
Revision as of 02:36, 15 October 2014
Main differences between original (command line, C) Git and JGit (EGit).
- JGit does not support any SVN bridging operations. There is a feature request discussed in bug 315264. The most common ones (svn rebase, svn fetch, svn dcommit) can be handled with external launchers.
- JGit does not support bundles in any way - they can't be created pulled, or queried. There are no current plans to add bundle support.
- JGit supports the merge strategies "resolve" and "recursive"
- JGit is missing support for a number of configuration settings, including most of the ones related to merging. The list of some of them:
- 'push.default' no supported.
- Hooks are not currently supported.
- Creation of light-weight and signed tags is not supported (bug 386908).
- Creation of signed commits is not supported (bug 382212).
- When a directory is deleted from the working set, EGit will immediately remove it from the working tree and stage the deletion of the files. If you want to undo this you must manually recreate the deleted directory first. At that point you can use standard egit tools to recover the deleted files. [this one might be obsolete]