Hi, Axel, Clément and I are french Ensimag students ( http://ensimag.grenoble-inp.fr/ ) working for the community on the occasion of an end-of-year project (in equivalent of master 1). So it is kind of a mini-google summer of code for us. We are mentored by Matthieu Moy who introduced us in the thread: http://article.gmane.org/gmane.comp.version-control.git/147487/ We are currently working on a textconv support for git-blame. We are getting to a first version that we will soon communicate. Afterwards, we thought about working on git-merge. Actually, when having some local changes in some files that would be overwritten by merge, git-merge aborts giving the first file for which there is a problem. If we commit or stash the changes on this file and try again to merge, the second file for which there are some local changes will appear. What will we try to do is to provide to the user a list of all the files for which there is a problem before aborting. Do you think it is a good idea? Thank you all for your time. Cheers, Axel, Clément and Diane -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html