# Re: [PATCH v6 2/2] patch-id: replace `atoi()` with `strtoi_with_tail()` 4 messages from 2024-03-13 to 2024-03-18. Participants: Mohit Marathe, Junio C Hamano. Thread: https://gitlist.dev/t/61111 ## Mohit Marathe, 2024-03-13 15:01 Subject: Re: [PATCH v6 2/2] patch-id: replace `atoi()` with `strtoi_with_tail()` Message-ID: URL: https://gitlist.dev/e/boJAHbg3xUqJ1hriFJu3QNlF9CYWbP9x9zu9mcV1jk1SI2WGAOes-wU1MMBZBWvMxs6VTkhlfE59iMEnYcDTOUTxA-3M72kvOJN613jaygw%3D%40proton.me ``` Hi, I am writing to inquire about the status of this patch. As a contributor, I am curious whether the decision not to merge this patch was intentional or if it might have been overlooked. Could you kindly provide some clarity on this matter? I tried finding this on "What's cooking in Git" but couldn't find it. If there are any specific reasons for not merging the patch, I would be grateful if you could share them. Additionally, if there are any further corrections needed please do let me know. Thanks, Mohit ``` ## Junio C Hamano, 2024-03-14 08:08 Subject: Re: [PATCH v6 2/2] patch-id: replace `atoi()` with `strtoi_with_tail()` Message-ID: URL: https://gitlist.dev/e/xmqq34st1bhh.fsf%40gitster.g In-Reply-To: ``` Mohit Marathe writes: > I am writing to inquire about the status of this patch. Thanks for pinging. Please be kind to fellow project members by including a URL under https://lore.kernel.org/git/ to the original discussion. In general there needs to be a reason why a patch should be applied, but a lack of reason why a patch should be applied is good enough reason why a patch may not have been applied so far. I cannot offhand recall what problems the patch had or if there were additional problems in the patch that was left unaddressed. Thanks. ``` ## Mohit Marathe, 2024-03-14 10:22 Subject: Re: [PATCH v6 2/2] patch-id: replace `atoi()` with `strtoi_with_tail()` Message-ID: URL: https://gitlist.dev/e/jnBS0qo8QZFzqzU38VOg0t-BVquGuzjDdY820B8DW1uCd70FAetOik5rSV01nzSidyMqIPbarZ7lL9JNra-hR8Xzdfv9ZLcLI9wU3nyVgrI%3D%40proton.me In-Reply-To: ``` > Mohit Marathe mohitmarathe@proton.me writes: > > > I am writing to inquire about the status of this patch. > > > Thanks for pinging. > > Please be kind to fellow project members by including a URL under > https://lore.kernel.org/git/ to the original discussion. In general I thought replying in the same thread as that of patch would be enough. But now that I think about it, threads can get pretty long. My bad,I will keep in mind to include the URL of the patch next time. Just for the record, I was talking about this patch: https://lore.kernel.org/git/pull.1646.v6.git.1707025718.gitgitgadget @gmail.com/ > there needs to be a reason why a patch should be applied, but a lack > of reason why a patch should be applied is good enough reason why a > patch may not have been applied so far. I cannot offhand recall > what problems the patch had or if there were additional problems in > the patch that was left unaddressed. > > Thanks. This makes perfect sense. Thanks for clarifying. Thanks. ``` ## Junio C Hamano, 2024-03-18 15:27 Subject: Re: [PATCH v6 2/2] patch-id: replace `atoi()` with `strtoi_with_tail()` Message-ID: URL: https://gitlist.dev/e/xmqq7chzlfvp.fsf%40gitster.g In-Reply-To: ``` Mohit Marathe writes: > I thought replying in the same thread as that of patch would be enough. Well, if you look at the headers of your message, there only is its own Message-ID and no In-Reply-To or References, which some/many MUAs go by. > Just for the record, I was talking about this patch: > https://lore.kernel.org/git/pull.1646.v6.git.1707025718.gitgitgadget > @gmail.com/ Yup, thanks. I ended up at the same place with subject search ;-) ```