From: Jonathan Nieder <jrnieder@gmail.com>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org, Christian Couder <chriscool@tuxfamily.org>
Subject: "libify part of reset" mini-series (Re: What's cooking in git.git (Jun 2011, #02; Sat, 11))
Date: Sun, 12 Jun 2011 19:17:37 -0500 [thread overview]
Message-ID: <20110613001737.GA2291@elie> (raw)
In-Reply-To: <BANLkTinHCX0vmAdk+su-_Y0th9vLQ6qsnw@mail.gmail.com>
Hi,
Ramkumar Ramachandra wrote:
> Have you seen my "libify reset" patch [1]? I thought it was an easy candidate.
I don't think it is one, personally. While it is good to get feedback
on such things early, that patch exposes some functions without making
the API much clearer and without any users to explain how they work in
practice. I think it is best to let such patches cook in a private
branch until there is some obvious benefit to including them in git.
That benefit doesn't necessarily have to be new code using it --- it
could be increased clarity, faster compile times, decreasing the delta
with libgit2 so later fixes can be ported between the two more easily,
anything. Though in this case, I'm guessing the motivation from your
end is the code that uses it, so that's an obvious choice.
I'd suggest sending it again for inclusion when the code that uses it
is ready, or for review whenever you have questions that the list can
answer.
next prev parent reply other threads:[~2011-06-13 0:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-12 6:49 What's cooking in git.git (Jun 2011, #02; Sat, 11) Junio C Hamano
2011-06-12 12:14 ` Ramkumar Ramachandra
2011-06-13 0:17 ` Jonathan Nieder [this message]
2011-06-13 13:16 ` Junio C Hamano
2011-06-12 16:18 ` Sverre Rabbelier
2011-06-13 15:25 ` Junio C Hamano
2011-06-13 16:07 ` Sverre Rabbelier
2011-06-14 4:27 ` Elijah Newren
2011-06-16 21:05 ` Jeff King
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=20110613001737.GA2291@elie \
--to=jrnieder@gmail.com \
--cc=artagnon@gmail.com \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).