From: "Pavel Raiskup" <xraisk00@gmail.com>
To: "Vicent Marti" <vicent@github.com>,
"Jonathan Nieder" <jrnieder@gmail.com>
Cc: git@vger.kernel.org, "Jeff King" <peff@peff.net>,
"Ramkumar Ramachandra" <artagnon@gmail.com>
Subject: Re: Histogram diff, libgit2 enhancement, libgit2 => git merge (GSOC)
Date: Tue, 22 Mar 2011 17:43:42 +0100 [thread overview]
Message-ID: <op.vsq7e4og2m56ex@localhost.localdomain> (raw)
In-Reply-To: <20110321012708.GA18323@elie>
Hello,
Jonathan Nieder wrote:
> Vicent Marti wrote:
>
>> -- I'm
>> personally doubtful of anybody succeeding on doing that project during
>> the SoC,
>
> ...
> If someone wants to work on this, I'd be glad to talk over what would
> be needed to make a realistic proposal.
>
>> so I have very little interest on mentoring the task.
>
> That's okay, of course. What's probably important for people
> considering this project is: would you be willing to answer questions
> and consider patches from a person working on this? That is, do you
> consider the goal even worthwhile?
>
> I am probably not the best person to mentor this but if no one else
> wants to then I would be interested.
As I can see now, it could be quite too heavy for me to produce
results as good as would be needed. This is probably quite difficult
task for starting with git contributing. Rather considering the other
git-topics for now (but I'm not rejecting this idea yet).
> A good place to start is the initial commit e83c516 (Initial revision
> of "git", the information manager from hell, 2005-04-07).
> ........
> Heh, probably I didn't choose the best example. :) A short article
> about this in Documentation/technical certainly wouldn't be a bad
> thing.
>
> In addition to "git log -S" as used above, I tend to find "git blame -L"
> helpful FWIW. And people on the list can be helpful, too.
This "short" article is very helpful, thank you for that! I think
it can help all contributors (not only students) at the beginning
of their git journey.
>> b) Write a minimal Git client using libgit2. Peff keeps bringing this
>> up and I think it's a bangin' good idea. Write something small and
>> 100% self contained in a C executable that runs everywhere with 0
>> dependencies -- don't aim for full feature completion, just the basic
>> stuff to interoperate with a Git repository.
>
> I agree that this would be very neat, too.
The idea of git client based on libgit2 sounds VERY interesting. I'm
going to ask for some details in neighboring sub-thread.
>> Best of luck with your application process with whatever project you decide,
>> Vicent
>
> Seconded. :)
Thank you both, I'm not going to try other projects, there is not enough
time now for researching other projects and git is my only choice and desire.
Pavel
next prev parent reply other threads:[~2011-03-22 16:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-20 10:55 Histogram diff, libgit2 enhancement, libgit2 => git merge (GSOC) Pavel Raiskup
2011-03-20 18:06 ` Shawn Pearce
2011-03-22 12:32 ` Pavel Raiskup
2011-03-20 18:25 ` Junio C Hamano
2011-03-20 21:01 ` Vicent Marti
2011-03-20 23:44 ` Jeff King
2011-03-21 0:38 ` Vicent Marti
2011-03-22 17:32 ` Pavel Raiskup
2011-03-22 18:47 ` Jeff King
2011-03-22 19:18 ` Junio C Hamano
2011-03-21 1:27 ` Jonathan Nieder
2011-03-22 16:43 ` Pavel Raiskup [this message]
2011-03-23 0:24 ` Vincent van Ravesteijn
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=op.vsq7e4og2m56ex@localhost.localdomain \
--to=xraisk00@gmail.com \
--cc=artagnon@gmail.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=peff@peff.net \
--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).