All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.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:51:08 -0700	[thread overview]
Message-ID: <7vtydwaezn.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <BANLkTimg-a-k8wR-gotEYUQ+C3LcwsBGuw@mail.gmail.com> (David Chanters's message of "Sun, 17 Apr 2011 16:13:45 +0100")

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?

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.

      parent reply	other threads:[~2011-04-17 18:51 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
2011-04-17 18:51 ` Junio C Hamano [this message]

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=7vtydwaezn.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.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.