{"thread":{"id":"62298","subject":"Fwd: Git bug","startedAt":"2024-10-09T18:04:20Z","lastAt":"2024-10-09T20:21:05Z","messageCount":2,"participants":["Amith Ashok","Kristoffer Haugsbakk"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"504619","messageId":"CAHoc8a8b2o7eJULhoF+5VM15ickjRY_f=WBmpPsG=0kwrx1CfQ@mail.gmail.com","threadId":"62298","inReplyTo":"CAHoc8a8JQd=c0bD5Yneg8R7tEjETyns-yyWjP=V3TTn9R48Nzg@mail.gmail.com","subject":"Fwd: Git bug","fromName":"Amith Ashok","fromEmail":"amithashok8@gmail.com","sentAt":"2024-10-09T18:04:08Z","receivedAt":"2024-10-09T18:04:20Z","isPatch":false,"sender":{"key":"amithashok8@gmail.com","avatar":null},"body":"Hi ,\n\nI wanted to report a git bug that I encountered today .\n\nI created a feature branch from a release branch before my peer\ncommitted to it . My peer committed to this branch through the lower\nbranches of auto merge option to this high branch .\n\nHowever when I do a git  pull I was facing the issue in of the files.\nI tried multiple ways to debug this but ultimately found that the\nissue is with got itself .\n\nI took the a fresh branch from this branch (post merge of my friend )\nthen the error does not occur.\n\n\nI appreciate if you look into this . And if this indeed is an issue\ncould you fix it and you acknowledge my original receipt as the\nfindings to this .\n\n\nThanks\nAmith Ashok Chugani\n"},{"id":"504637","messageId":"6b1f434a-fb56-4699-a03a-069a1da118ab@app.fastmail.com","threadId":"62298","inReplyTo":"CAHoc8a8b2o7eJULhoF+5VM15ickjRY_f=WBmpPsG=0kwrx1CfQ@mail.gmail.com","subject":"Re: Fwd: Git bug","fromName":"Kristoffer Haugsbakk","fromEmail":"kristofferhaugsbakk@fastmail.com","sentAt":"2024-10-09T20:20:43Z","receivedAt":"2024-10-09T20:21:05Z","isPatch":false,"sender":{"key":"kristofferhaugsbakk@fastmail.com","avatar":null},"body":"On Wed, Oct 9, 2024, at 20:04, Amith Ashok wrote:\n> Hi ,\n>\n> I wanted to report a git bug that I encountered today .\n>\n> I created a feature branch from a release branch before my peer\n> committed to it . My peer committed to this branch through the lower\n> branches of auto merge option to this high branch .\n>\n> However when I do a git  pull I was facing the issue in of the files.\n\nWhat issue?\n\nUsually a git(1) bug can be reproduced with a set of commands\n(reproduction).  And some part of the output demonstrates that there is\na bug.  Which could be:\n\n- The output itself tells you it’s a `BUG` (code path that should be\n  unreachable)\n- The output or behavior is unreasonable or unexpected given the context\n\nThen you provide it here in the bug report.  Like:\n\n```\nBUG: this should never happen but it did (<file>:<line>)\n```\n\nThere’s also git-bugreport(1) which you can use to fill out such a\nreport.  That will record things like your Git version and other\nrelevant system info.\n\n> I tried multiple ways to debug this but ultimately found that the\n> issue is with got itself .\n>\n> I took the a fresh branch from this branch (post merge of my friend )\n> then the error does not occur.\n>\n>\n> I appreciate if you look into this . And if this indeed is an issue\n> could you fix it and you acknowledge my original receipt as the\n> findings to this .\n\nIt is standard to credit bug reporters in this project.\n\n>\n>\n> Thanks\n> Amith Ashok Chugani\n\n-- \nKristoffer Haugsbakk\n\n"}]}