On Fri, Aug 1, 2008 at 3:11 PM, Alexander Litvinov <litvinov2004@gmail.com> wrote:No, you should do any conversion here. There are two reasons for that: 1. If you do then you will not be able to apply binary patches later. 2. You do not really need it if the SVN repository has correct eol settings, because all files that have svn:eol-style set to either 'native' or 'LF' will have LF. Those that do not have svn:eol-style or have it to another value should not be subject to CRLF conversion at all. So, I believe all files received from SVN should be stored as is. Import is not about creating new commits, it is about getting history from another repository as it is. It is done only for files that do not have CRLF already. It is okay for Git to store CRLF, because you want to treat them as binary files. If you want them being treated as text, you should change svn:eol-style to 'native' for those files in SVN and then new versions of these files will have the right ending. It is how SVN client works. The only problem is how to synchronize the SVN view which files are binary and which are text and what Git thinks about them. Dmitry -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
| david | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg Kroah-Hartman | [PATCH 001/196] Chinese: Add the known_regression URI to the HOWTO |
| Trent Piepho | Re: [PATCH] [POWERPC] Improve (in|out)_beXX() asm code |
| Steven Rostedt | Re: -rt scheduling: wakeup bug? |
| Andrew Morton | Re: [BUG] New Kernel Bugs |
| Gerrit Renker | [PATCH 0/37] dccp: Feature negotiation - last call for comments |
| David Miller | [GIT]: Networking |
git: | |
