From: <dag@cray.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Andreas Ericsson <ae@op5.se>, <greened@obbligato.org>,
<git@vger.kernel.org>
Subject: Re: libgit2 status
Date: Mon, 27 Aug 2012 11:13:12 -0500 [thread overview]
Message-ID: <nnglih0jotj.fsf@transit.us.cray.com> (raw)
In-Reply-To: <7vharpv77n.fsf@alter.siamese.dyndns.org> (Junio C. Hamano's message of "Sun, 26 Aug 2012 11:28:12 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> And the last one should really be a "longer term" item. It is more
> important for its codebase to get mature and robust, and that can
> only happen by various projects and products (e.g. GitHub for Mac)
> using it to improve it. I do not think "subtree" (or anything in
> contrib/ for that matter) is part of "the core stuff of git", and do
> not see a problem; such a move may help both subtree and libgit2.
>
> Over a much longer timeperiod, I wouldn't be surprised if some "core
> stuff" gets reimplemented on top of libgit2 and distributed as part
> of the git-core.
I am hoping to move git-subtree into core once it performs a little
better and I've fixed a couple of bugs. Will basing it on libgit2 delay
that process significantly? Six months delay is no problem. 2 years
would be problematic.
I would be happy to be a guinea pig for libgit2 in order to improve it,
but I don't want to significantly impact git-subtree's move to core.
I'll have to figure out the right balance there given feedback.
-Dave
next prev parent reply other threads:[~2012-08-27 16:20 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-24 14:02 libgit2 status greened
2012-08-25 9:56 ` Andreas Ericsson
2012-08-25 20:46 ` Vicent Marti
2012-08-25 21:46 ` Nicolas Sebrecht
2012-08-25 22:32 ` Carlos Martín Nieto
2012-08-26 7:26 ` Elia Pinto
2012-08-26 18:28 ` Junio C Hamano
2012-08-26 18:56 ` Junio C Hamano
2012-08-27 16:13 ` dag [this message]
2012-08-27 17:10 ` Junio C Hamano
2012-08-27 18:49 ` dag
2012-08-27 19:44 ` Junio C Hamano
2012-08-27 21:21 ` dag
2012-08-27 21:40 ` Nicolas Sebrecht
2012-08-28 17:59 ` dag
2012-08-28 18:36 ` Junio C Hamano
2012-10-19 0:42 ` Thiago Farina
2012-10-19 3:54 ` Ramkumar Ramachandra
2012-10-19 20:13 ` Junio C Hamano
2012-10-19 22:11 ` dag
2012-10-19 22:43 ` Junio C Hamano
2012-10-20 1:21 ` Thiago Farina
2012-10-20 7:58 ` Andreas Ericsson
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=nnglih0jotj.fsf@transit.us.cray.com \
--to=dag@cray.com \
--cc=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=greened@obbligato.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.