{"thread":{"id":"38551","subject":"[poll] does anybody depend on RelNotes being a symbolic link?","startedAt":"2015-02-11T22:23:55Z","lastAt":"2015-02-11T22:23:55Z","messageCount":1,"participants":["Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"255949","messageId":"xmqqegpwt7d0.fsf@gitster.dls.corp.google.com","threadId":"38551","inReplyTo":null,"subject":"[poll] does anybody depend on RelNotes being a symbolic link?","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2015-02-11T22:23:55Z","receivedAt":"2015-02-11T22:23:55Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"I am wondering if I can turn the top-level RelNotes symbolic link\ninto a regular file.\n\nThe benefit for doing that is that I can start the file like so:\n\n    Git ???? Release Notes\n    ======================\n\n    Updates since v2.3\n\nearly in the cycle and then later decide if we want to make the next\none 3.0 or 2.4.  And then just after the release, I move it down to\nDocumentation/RelNotes/3.0.0.txt (or 2.4.0.txt) and start the next\ncycle.\n\nOne thing that worries me is that people and their build scripts\nmight depend on being able to figure out the upcoming release name\nby reading the symbolic link, assuming that the link would point to\nDocumentation/RelNotes/x.y.z.txt, and such a change ends up breaking\ntheir setup.  I am not sure how likely this would be.  Objections?\n\nAlso any other objections, other possible cause of breakages I may\nhave missed?\n"}]}