merge flags all files as modified [message #666110] |
Tue, 19 April 2011 03:39  |
Eclipse User |
|
|
|
Hi all,
I wonder if this is a normal behaviour. Each time I merge 2 branches (either from same repo or from origin), I have all my files flagged as changed and must commit them all.
Is it really the way it should work? It's hard after that to verify if the merge was correctly done because we don't have a way to quickly see what changed.
Max
|
|
|
|
Re: merge flags all files as modified [message #666141 is a reply to message #666129] |
Tue, 19 April 2011 06:08   |
Eclipse User |
|
|
|
I don't have access to github inside the company. However, I could reproduce the problem with a brand new repository.
Here are my steps:
1.Created the repository using "git extensions"
2. creates a Java project in repository
3. share the project
4. add 3 classes: A, B, C
5. create "work" branch, checkout
6. edit A, commit
7. checkout master
8. edit B, commit
9. checkout "work"
10. edit A, commit
11. checkout master
12. merge with "work"
now all files are marked "Mod., not staged", including C.java, .classpath and .project.
eGit + jGit versions = 0.11.3
Can you reproduce it?
I created Bug 343253
Max
|
|
|
|
|
Re: merge flags all files as modified [message #667849 is a reply to message #666581] |
Mon, 02 May 2011 08:53  |
Eclipse User |
|
|
|
EGit is definitively supposed to be interoperable with native git.
I don't use gitextensions so I don't know if it brings some problems into this game.
Maybe gitextensions sees some different configuration for
core.fileMode, core.ignorecase, core.eol, core.safecrlf, core.autocrlf [1]. Or your two branches only differ in line endings ? How do these changes you have to commit look like (double click on files in the file list of the commit dialog to open a diff view) ?
[1] http://www.kernel.org/pub/software/scm/git/docs/git-config.h tml
|
|
|
Powered by
FUDForum. Page generated in 0.05368 seconds