git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Ericsson <ae@op5.se>
To: Evgeniy Ivanov <powerfox@kde.ru>
Cc: Shawn Pearce <spearce@spearce.org>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: git integration with monodevelop
Date: Thu, 13 Nov 2008 08:20:18 +0100	[thread overview]
Message-ID: <491BD532.9090200@op5.se> (raw)
In-Reply-To: <491B02FF.2060204@kde.ru>

Evgeniy Ivanov wrote:
> Andreas Ericsson wrote:
>> Evgeniy Ivanov wrote:
>>> Hi Andreas,
>>> I've developed basic git-support in KDevelop using git's cmd-line
>>> interface. I'm very interested in rewriting it with libgit2, when
>>> libgit2 becomes usable. Can you, please, drop me a line, when you have
>>> some code?
>>>
>> git clone http://www.spearce.org/projects/scm/libgit2/libgit2.git
>>
>> will probably prove beneficial. I'm adding Shawn to Cc as he's the
>> primary libgit2 author. Please follow the git.git guidelines for
>> submitting patches, and please note that there's not much there
>> right now. Adding a wishlist for what you need in terms of UI
>> integration might make it easier to focus on something when it's
>> going slow.
>>
> 
> I can only suggest something like this on top of library (something like
>  common used things):
> http://websvn.kde.org/trunk/KDE/kdevplatform/plugins/git/gitexecutor.h?revision=856589&view=markup
> 
> I Don't think library interface should be much differ from cmd-line's one.

Well, it will be. The git CLI is inconsistent in places but it would be
weird to have libgit2 inherit those inconsistencies.

> For advanced use, QGit's includes can be used (search commit objects,
> etc). QGit has much more features, than my integration. AFAIK Shawn has
> experience in egit

Yes. He wrote it.

> (and maybe even gitk). IMHO the best thing is to
> implement libgit2 in terms of QGit, egit and maybe kdevelop's git
> support.

That would defeat the purpose rather wildly. The idea with libgit2 is
to create a library that the git cli can use, so building it based on
command-line output is a no-go. libgit2 is the attempt to make it right.

> I will help with pleasure (mentored by Shawn), when have some
> time (maybe only in January-February).
> 

Excellent :)

> But this is the same things Shawn has suggested to my mentor and me at
> the beginning of SoC...
>

Oh? I didn't know libgit2 started as a SoC project.

-- 
Andreas Ericsson                   andreas.ericsson@op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231

  parent reply	other threads:[~2008-11-13  7:21 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-12 10:22 git integration with monodevelop Andreas Ericsson
2008-11-12 10:31 ` Andreas Ericsson
2008-11-13  0:00   ` Govind Salinas
2008-11-12 19:48 ` [MonoDevelop] " Miguel de Icaza
2008-11-12 22:19   ` Jakub Narebski
2008-11-13  1:42     ` Miguel de Icaza
2008-11-14 13:26       ` [MonoDevelop] " Johannes Schindelin
2008-11-14 17:28         ` Miguel de Icaza
2008-11-14 17:55           ` [MonoDevelop] " Jakub Narebski
2008-11-14 17:53         ` "Andrés G. Aragoneses"
2008-11-12 23:56 ` Michael Hutchinson
2008-11-13  7:55   ` Andreas Ericsson
2008-11-13  9:28     ` Christian Hergert
2008-11-13 11:01       ` [MonoDevelop] " Andreas Ericsson
2008-11-13 16:10         ` Lluis Sanchez Gual
     [not found] ` <491AF20D.4070600@kde.ru>
     [not found]   ` <491AF768.3010607@op5.se>
     [not found]     ` <491B02FF.2060204@kde.ru>
2008-11-13  7:20       ` Andreas Ericsson [this message]
2008-11-14 13:30         ` Johannes Schindelin
2008-11-14 13:53           ` Andreas Ericsson
2008-11-14 14:55             ` Johannes Schindelin

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=491BD532.9090200@op5.se \
    --to=ae@op5.se \
    --cc=git@vger.kernel.org \
    --cc=powerfox@kde.ru \
    --cc=spearce@spearce.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).