{"thread":{"id":"20814","subject":"[JGIT] potential incompatibility with old git repos.","startedAt":"2009-09-01T21:07:56Z","lastAt":"2009-09-01T21:07:56Z","messageCount":1,"participants":["Mark Struberg"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"122261","messageId":"723287.10285.qm@web27802.mail.ukl.yahoo.com","threadId":"20814","inReplyTo":null,"subject":"[JGIT] potential incompatibility with old git repos.","fromName":"Mark Struberg","fromEmail":"struberg@yahoo.de","sentAt":"2009-09-01T21:07:56Z","receivedAt":"2009-09-01T21:07:56Z","isPatch":false,"sender":{"key":"struberg@yahoo.de","avatar":"https://gravatar.com/avatar/119742c3e8dbc8db35a92bdff0581aec8d364d415f770e60431cba262daa974f?d=mp&s=160"},"body":"Hi Shawn, Robin!\n\nI'm happy to spend some time on the maven-scm-providers-jgit again, but spotted a problem with running the latest version of JGIT on my test repository [1]. This test repo has been created a good while ago (~nov 2007) with git 1.3.54 or so and has been edited on various computers.\n\nIt works with native git but crashes with both SimpleRepository#clone [2] and jgit.\n\njgit fails with \"cannot checkout; no HEAD advertised by remote\"\nin guessHEAD\n\nJGIT used to work on this repo until a few weeks. I tracked it down with git bisect and found commit\n72b1f0d334729a49cc52e4762093148be62bea39\nto be the bad one.\n\nI glimpsed at the code and it appears that the new code in RefDatabase#readLine is not Windows CR+LF aware. (This hits me although I use Linux because our SVN at apache.org seems to have it stored with CR+LF.)\n\nPatch will follow.\n\ntxs and LieGrue,\nstrub\n\n\n[1] http://github.com/struberg/maven-scm-providers-git/tree/a66e9470ea087030bb8bd40edb2cab22a2de0e6a/maven-scm-provider-gittest/src/main/resources/repository/test-repo\n[2] http://github.com/sonatype/JGit/tree/struberg\n\n\n      \n"}]}