Dan Newcome, blog

I'm bringing cyber back

Git newline handling between platforms

with one comment

Previously, I had written/complained about the way that the Git version control system handled newline characters. I wanted to update that with some new information here. The cause of my frustration back then was that I hadn’t created my working copy correctly. I had been under the assumption that since each Git repository is a standalone repository that I could just copy the whole thing around my network using a simple file copy. You can do it that way, but there is a catch: if there are files in the working directory, ie, there are files `checked out’, you will have issues copying files between systems. Note that having files checked out on a `central’ repository, ie one that you want to `push’ changes to, can also cause lots of problems. In general, although Git is a distributed system, and each repository is technically a `peer’, in practice certain repositories should not have their own working directories.

I had been using Mercurial in a quick and dirty way, where I would make a copy of the whole repository quickly using a simple file copy before working on a project. Now that I’m using Git, I simply settled into that old (bad) habit of copying stuff around and ran into the newline issue when trying to commit files that had been checked out on a Linux system, copied along with the repository to a Windows box, and modified.

The correct way of handling the situation is to make sure that all changes are committed to the remote repository, and then create the local repository using `git clone’. When using Git on Windows via the msysgit port, you can use UNC paths. Thus, there is not really much of an excuse to rely on file copy when you can do:

C:\>git clone //myserver/repos/foo.git

Note that all backslashes are written as forward slashes according to Posix convention rather than Windows.

I still don’t like the fact that Git insists on translating newline conventions when working between platforms, but I’ve read that Git places a high priority on data consistency and safeguarding against corruption, so I guess I’ll just be reassured that a lot of people that are smarter than me are looking out on this one.

For more information about how Git handles newlines, this page on GitHub is a good start.


Written by newcome

December 19, 2009 at 2:58 pm

Posted in Uncategorized

One Response

Subscribe to comments with RSS.

  1. […] with one comment UPDATE: I’ve added a post that addresses the cause of my issues here. […]

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: