git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vincent van Ravesteijn <vfr@lyx.org>
To: "Motiejus Jakštys" <desired.mta@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: start of git2 (based on libgit2)
Date: Sat, 26 Mar 2011 00:54:25 +0100	[thread overview]
Message-ID: <4D8D2B31.4040908@lyx.org> (raw)
In-Reply-To: <20110325231203.GA7961@jakstys.lt>

On 26-3-2011 0:12, Motiejus Jakštys wrote:
> Hello,
>
> I wrote similar letter before, but did not receive feedback I was expecting.

I wrote a mail on the same topic to the libgit2@librelist.org 
mailinglist, because I got interested in the same project (although I 
will not be a GSoC student).

http://librelist.com/browser/libgit2/
> According to Jeff King[2], I should start with plumbing commands. I
> agree.  However, how deep?  I.e. do I have to make sure all git rev-list
> possible arguments are implemented?

I guess a lot can be copied from Git itself. Actually builtin/rev-list.c 
consists mostly of command line arguments parsing methods, and 
outputting functions. The key is to parse what you want to know and ask 
libgit2 to provide the info. If libgit2 has implemented the basic 
functionality that is needed, the rest would be relatively simple.

> Are we aiming for a distributed 100s of executables architecture
> (current git), or single huge binary? I would go for single executable
> for to higher portability. Is that ok?

AFAICS, current git is a single binary on Windows already.

> Build tool. Currently libgit2 uses waf. I am not against it (I've chosen
> waf for one of my own C++ projects), However, it's too clumsy for me. Is
> it me who lacks experience? Scons looks much easier for me. Moreover, we
> do not need automatic configuration, so it makes waf "overfeatured".

Why not CMake which is also used for libgit2 ?

I already wrote a CMakeLists file for your git2 app.

> I am a student and would like to do this take this up in GSOC. I just
> received a letter from Vicent Marti with sort of confirmation that the
> project is interesting for the community.

As you know, this project can be possibly fulfilled by a GSoC student 
(either you or someone else). Maybe people are awaiting this before 
diving into the project.

Vincent

  reply	other threads:[~2011-03-25 23:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-25 23:12 start of git2 (based on libgit2) Motiejus Jakštys
2011-03-25 23:54 ` Vincent van Ravesteijn [this message]
2011-03-26  2:13   ` Motiejus Jakštys
2011-03-26 13:29   ` Jeff King
2011-03-27  8:34     ` Junio C Hamano
2011-03-27  9:56       ` Vincent van Ravesteijn
2011-03-26  6:33 ` Sam Vilain

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=4D8D2B31.4040908@lyx.org \
    --to=vfr@lyx.org \
    --cc=desired.mta@gmail.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 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).