| core.autocrlf now supported in egit/jgit? [message #815460] |
Wed, 07 March 2012 12:40  |
Eclipse User |
|
|
|
I was under the impression that core.autocrlf was not supported, but it looks like it might be now. At least it seems to be working correctly with one team where some developers use OS X (config option set to 'input') and some use Windows (config option set to 'true'). This is with JGit 2.0.0.201203070519.
Is it safe to assume we can rely on this as of 2.0 ?
|
|
|
|
| Re: core.autocrlf now supported in egit/jgit? [message #817047 is a reply to message #816981] |
Fri, 09 March 2012 10:15  |
| Eclipse User |
|
|
|
Personally I have no problem telling users they can rely on the software I release. To each his own...
Given the autocrlf is supported, the updated list of commonly used Git features not supported by egit has now shrunk to the following:
Commonly used operations that are not yet supported:
- stash
- svn
- bundle
- checkout <commit> -- <directory>
- reset <commit> -- <path>
except for the special case of resetting a single file to the HEAD revision
which can be done by unstaging workspace changes to that file.
Commonly used features that are not yet supported:
- Hooks
- Creation of light-weight and signed tags
- Most merge options, including -s, -ff, -no-ff, -ff-only.
- Merge strategies other than is 'resolve'.
- Most rebase options other than --abort.
- A number of configuration settings, including most of the ones related to merging,
|
|
|
Powered by
FUDForum. Page generated in 0.03345 seconds
Home