{"issue":{"state":"closed","pull_request":{"diff_url":"https://github.com/sitaramc/gitolite/pull/25.diff","html_url":"https://github.com/sitaramc/gitolite/pull/25","patch_url":"https://github.com/sitaramc/gitolite/pull/25.patch"},"milestone":null,"user":{"avatar_url":"https://secure.gravatar.com/avatar/1d2f55118d33495b73c30b1bb9e4540a?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"1d2f55118d33495b73c30b1bb9e4540a","url":"https://api.github.com/users/mohamedmansour","login":"mohamedmansour","id":68524},"assignee":null,"updated_at":"2011-11-16T00:55:17Z","labels":[],"closed_at":"2011-11-16T00:55:17Z","comments":1,"url":"https://api.github.com/repos/sitaramc/gitolite/issues/25","body":"Using Msysgit bash shell on Windows, passing in a file into\r\nsetperms confuses Gitolite since it doesn't parse out the\r\npermissions correctly since it contains Windows CR Line Feed.\r\nIt saves it correctly, but cannot verify it in the regex.\r\n\r\nBy cleaning out any CR character when that gets inputed, solves\r\nthe problem. Mysgit clients can continue using the default\r\nsettings. They could easily fix this issue by setting their\r\neditors to LF instead of CR but that isn't by default.","html_url":"https://github.com/sitaramc/gitolite/issues/25","title":"Support Windows Line Endings in Gitolite.","number":25,"id":767269,"created_at":"2011-04-14T02:59:20Z"},"action":"created","comment":{"user":{"avatar_url":"https://secure.gravatar.com/avatar/f731ab5313beb6fd680c8a9a51612925?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"f731ab5313beb6fd680c8a9a51612925","url":"https://api.github.com/users/sitaramc","login":"sitaramc","id":43316},"updated_at":"2011-11-16T00:55:17Z","url":"https://api.github.com/repos/sitaramc/gitolite/issues/comments/2754093","body":"was added later, though not by this patch","id":2754093,"created_at":"2011-11-16T00:55:17Z"}}