From: "Motiejus Jakštys" <desired.mta@gmail.com>
To: git@vger.kernel.org
Subject: start of git2 (based on libgit2)
Date: Fri, 25 Mar 2011 23:12:03 +0000 [thread overview]
Message-ID: <20110325231203.GA7961@jakstys.lt> (raw)
Hello,
I wrote similar letter before, but did not receive feedback I was expecting.
I think libgit2 is an amazing thing, and I started writing[1] cli client for
it. This is what it can do now:
$ git2 rev-list <anything>
Which is roughly equivalent to:
$ git rev-list HEAD
I do not know how it will figure out past merge history, but that's for
the future.
I want to get started with it, but before that I want and discuss some
architectural questions.
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?
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?
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".
Build configuration. Git-send-email is not really a must-have for an
embedded device, so we should be able to specify these features in
configure-time. How do you think it should be taken care of?
1) <buildtool> configure --disable-everything --enable-email
2) make menuconfig and enjoy the blue screen of choice
3) anything else?
Waiting for your answers, will go on working.
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. I'm happy about it. Currently
I am a full-time python programmer, but have done some C++. I created
SoundPatty[3], a real-time sound recognition (record) application for my
job VoIP recognition needs.
In case you have any questions, opinions, please ask. Thank you.
[1] https://github.com/Motiejus/git2/
[2] http://marc.info/?l=3Dgit&m=3D130081966214059&w=3D4
[3] https://github.com/Motiejus/SoundPatty/
[CV] http://m.jakstys.lt/
Motiejus Jakštys
next reply other threads:[~2011-03-25 23:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-25 23:12 Motiejus Jakštys [this message]
2011-03-25 23:54 ` start of git2 (based on libgit2) Vincent van Ravesteijn
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=20110325231203.GA7961@jakstys.lt \
--to=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).