{"thread":{"id":"9554","subject":"[ANNOUNCE] GIT MinGW port is now at v1.5.3-rc4","startedAt":"2007-08-16T09:43:37Z","lastAt":"2007-08-16T18:25:52Z","messageCount":4,"participants":["Johannes Sixt","Dmitry Kakurin","Johannes Schindelin"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"50870","messageId":"46C41C49.A92AEF07@eudaptics.com","threadId":"9554","inReplyTo":null,"subject":"[ANNOUNCE] GIT MinGW port is now at v1.5.3-rc4","fromName":"Johannes Sixt","fromEmail":"j.sixt@eudaptics.com","sentAt":"2007-08-16T09:43:37Z","receivedAt":"2007-08-16T09:43:37Z","isPatch":false,"sender":{"key":"j6t@kdbg.org","avatar":"https://avatars.githubusercontent.com/u/14810926?v=4"},"body":"I've just pushed an update of the MinGW port to:\n\nclone:  git://repo.or.cz/git/mingw.git\ngitweb: http://repo.or.cz/w/git/mingw.git\n\nThis passes the test suite, but I still haven't used it in production.\n\nThere are two additional changes that are of interest for the msysgit\neffort:\n\n- The test scripts no longer accept --no-symlinks becaust test-lib.sh\nauto-detects whether the file system supports symbolic links.\n\n- The devel branch no longer patches out libiconv, which is now required\nin the shipped configuration (the one from\nhttp://gnuwin32.sourceforge.net/packages/libiconv.htm, which requires\nthe OLD_ICONV setting in the Makefile).\n\n-- Hannes\n"},{"id":"50872","messageId":"6020F7321DB14F7B9288F0782A316803@ntdev.corp.microsoft.com","threadId":"9554","inReplyTo":"46C41C49.A92AEF07@eudaptics.com","subject":"Re: [ANNOUNCE] GIT MinGW port is now at v1.5.3-rc4","fromName":"Dmitry Kakurin","fromEmail":"dmitry.kakurin@gmail.com","sentAt":"2007-08-16T10:08:23Z","receivedAt":"2007-08-16T10:08:23Z","isPatch":false,"sender":{"key":"dmitry.kakurin@gmail.com","avatar":null},"body":"----- Original Message ----- \nFrom: \"Johannes Sixt\" <J.Sixt@eudaptics.com>\n> I've just pushed an update of the MinGW port to:\n> clone:  git://repo.or.cz/git/mingw.git\n\nWe need to make sure that we don't duplicate our efforts.\nHave you looked at http://repo.or.cz/w/git/mingw/4msysgit.git ?\nWe've made some progress while you were on vacation.\n\nAlso I think it's now time to merge two repos.\nTwo Johanneses (corresponding repo owners on the to: line), please coordinate with each other.\n\n- Dmitry\n"},{"id":"50876","messageId":"46C4332A.AF464A67@eudaptics.com","threadId":"9554","inReplyTo":"6020F7321DB14F7B9288F0782A316803@ntdev.corp.microsoft.com","subject":"Re: [ANNOUNCE] GIT MinGW port is now at v1.5.3-rc4","fromName":"Johannes Sixt","fromEmail":"j.sixt@eudaptics.com","sentAt":"2007-08-16T11:21:14Z","receivedAt":"2007-08-16T11:21:14Z","isPatch":false,"sender":{"key":"j6t@kdbg.org","avatar":"https://avatars.githubusercontent.com/u/14810926?v=4"},"body":"Dmitry Kakurin wrote:\n> \n> ----- Original Message -----\n> From: \"Johannes Sixt\" <J.Sixt@eudaptics.com>\n> > I've just pushed an update of the MinGW port to:\n> > clone:  git://repo.or.cz/git/mingw.git\n> \n> We need to make sure that we don't duplicate our efforts.\n> Have you looked at http://repo.or.cz/w/git/mingw/4msysgit.git ?\n> We've made some progress while you were on vacation.\n\nI've basically hiding under a stone when I was away. So, no, I didn't\nsee it until yesterday ;)\n\n> Also I think it's now time to merge two repos.\n> Two Johanneses (corresponding repo owners on the to: line), please coordinate with each other.\n\nSure! First thing I need to know is which branch I should keep an eye\non. master?\n\n-- Hannes\n"},{"id":"50899","messageId":"Pine.LNX.4.64.0708161922200.20400@racer.site","threadId":"9554","inReplyTo":"46C4332A.AF464A67@eudaptics.com","subject":"Re: [ANNOUNCE] GIT MinGW port is now at v1.5.3-rc4","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2007-08-16T18:25:52Z","receivedAt":"2007-08-16T18:25:52Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Thu, 16 Aug 2007, Johannes Sixt wrote:\n\n> Dmitry Kakurin wrote:\n> \n> > Also I think it's now time to merge two repos. Two Johanneses \n> > (corresponding repo owners on the to: line), please coordinate with \n> > each other.\n> \n> Sure! First thing I need to know is which branch I should keep an eye \n> on. master?\n\nAFAIAC 'master' is supposed to be for end-user consumption, and 'devel' is \nwhere all the action is (sort of our 'next' branch).\n\nBTW I just added you (Hannes) to the pushers list.\n\nCiao,\nDscho\n"}]}