From: Vincent van Ravesteijn <vfr@lyx.org>
To: Jeff King <peff@github.com>
Cc: Alexandru Sutii <sutii.alex@gmail.com>,
Vicent Marti <vicent@github.com>,
Jonathan Nieder <jrnieder@gmail.com>,
git@vger.kernel.org, libgit2@librelist.org
Subject: Re: GSoC questions
Date: Fri, 01 Apr 2011 23:05:13 +0200 [thread overview]
Message-ID: <4D963E09.10003@lyx.org> (raw)
In-Reply-To: <20110331192758.GD16981@sigill.intra.peff.net>
>> I guess the git2 client will consist solely of non-gitcore code, as
>> all the gitcore code will be part of libgit2 eventually.
>>
> I had sort of assumed that git-core code would be taken as inspiration,
> but that it would be an entirely new implementation, based around the
> error handling and build infrastructure provided by libgit2.
Looking at the above, I think we completely agree. When I wrote that the
gitcore code will get into libgit2, I indeed meant that it should be
rewritten in the libgit2 style and then be added to libgit2.
There was also temporarily the idea for GSoC to let Git use the
libgit2-library, or maybe to libify git on the road. That's why I
thought it might be useful if we were not going to rewrite the boring
administration code.
Thanks for thinking along,
Vincent
prev parent reply other threads:[~2011-04-01 21:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-27 9:20 GSoC questions Alexandru Sutii
2011-03-28 0:11 ` Jonathan Nieder
2011-03-28 14:35 ` Jeff King
2011-03-28 20:26 ` Alexandru Sutii
2011-03-28 20:52 ` Vicent Marti
2011-03-31 9:36 ` Alexandru Sutii
2011-03-31 11:06 ` Motiejus Jakštys
2011-03-31 11:58 ` Vincent van Ravesteijn
2011-03-31 18:34 ` Alexandru Sutii
2011-03-31 19:31 ` Jeff King
2011-03-31 19:27 ` Jeff King
2011-04-01 21:05 ` Vincent van Ravesteijn [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=4D963E09.10003@lyx.org \
--to=vfr@lyx.org \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=libgit2@librelist.org \
--cc=peff@github.com \
--cc=sutii.alex@gmail.com \
--cc=vicent@github.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).