From: Jakub Narebski <jnareb@gmail.com>
To: David Chanters <david.chanters@googlemail.com>
Cc: git@vger.kernel.org
Subject: Re: History for Strbuf and ParseOpts?
Date: Sun, 17 Apr 2011 11:19:31 -0700 (PDT) [thread overview]
Message-ID: <m3wriswxku.fsf@localhost.localdomain> (raw)
In-Reply-To: <BANLkTimg-a-k8wR-gotEYUQ+C3LcwsBGuw@mail.gmail.com>
David Chanters <david.chanters@googlemail.com> 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
next prev parent reply other threads:[~2011-04-17 18:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-17 15:13 History for Strbuf and ParseOpts? David Chanters
2011-04-17 18:19 ` Jakub Narebski [this message]
2011-04-17 18:51 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3wriswxku.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=david.chanters@googlemail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.