# History for Strbuf and ParseOpts? 3 messages from 2011-04-17 to 2011-04-17. Participants: David Chanters, Jakub Narebski, Junio C Hamano. Thread: https://gitlist.dev/t/27123 ## David Chanters, 2011-04-17 15:13 Subject: History for Strbuf and ParseOpts? Message-ID: URL: https://gitlist.dev/e/BANLkTimg-a-k8wR-gotEYUQ%2BC3LcwsBGuw%40mail.gmail.com ``` [ Please CC me on replies. Thanks! ]i, Hi, I shouldn't conflate to two (parseopts and strbuf) but can someone tell me how these two things came about -- that is, when/why/how? If I understand strbuf correctly, it's a transparent and dynamic way of handling strings? If so, how useful would it be as a separate project? TIA! David ``` ## Jakub Narebski, 2011-04-17 18:19 Subject: Re: History for Strbuf and ParseOpts? Message-ID: URL: https://gitlist.dev/e/m3wriswxku.fsf%40localhost.localdomain In-Reply-To: ``` David Chanters writes: > I shouldn't conflate to two (parseopts and strbuf) but can someone > tell me how these two things came about -- that is, when/why/how? If > I understand strbuf correctly, it's a transparent and dynamic way of > handling strings? If so, how useful would it be as a separate > project? I don't have a pointers to exchange of emails that started the road to strbuf and parseopt, but both are described in the techical documentation (GIT API Documents): Documentation/techical/* http://www.kernel.org/pub/software/scm/git/docs/technical/api-index.html http://www.kernel.org/pub/software/scm/git/docs/technical/api-strbuf.html http://www.kernel.org/pub/software/scm/git/docs/technical/api-parse-options.html -- Jakub Narebski Poland ShadeHawk on #git ``` ## Junio C Hamano, 2011-04-17 18:51 Subject: Re: History for Strbuf and ParseOpts? Message-ID: <7vtydwaezn.fsf@alter.siamese.dyndns.org> URL: https://gitlist.dev/e/7vtydwaezn.fsf%40alter.siamese.dyndns.org In-Reply-To: ``` David Chanters writes: > I shouldn't conflate to two (parseopts and strbuf) but can someone > tell me how these two things came about -- that is, when/why/how? I do this sort of digging fairly often. I am not going to do this particular one myself, but the general procedure is to first run "git log --diff-filter=A strbuf.[ch] parse-options.[ch]" to find which commits introduced them (hence, learn who did it, when and why), then go back to the list archive to find the discussions that lead to these changes. ```