git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Ericsson <ae@op5.se>
To: Christian Hergert <christian.hergert@gmail.com>
Cc: Michael Hutchinson <m.j.hutchinson@gmail.com>,
	monodevelop-list@lists.ximian.com,
	Git Mailing List <git@vger.kernel.org>,
	Shawn Pearce <spearce@spearce.org>
Subject: Re: [MonoDevelop] git integration with monodevelop
Date: Thu, 13 Nov 2008 12:01:34 +0100	[thread overview]
Message-ID: <491C090E.4070605@op5.se> (raw)
In-Reply-To: <6d4a25b10811130128r4ebf60a4s5679d06961b92450@mail.gmail.com>

Christian Hergert wrote:
> By unmanaged, he means the [DllImport] which you would need to do the call
> to the extern in the shared library.
> 
> Everyone that has chimed in has considered doing the git code before,
> believe us when we say we've thought about wrapping C.  In this case, it
> will be far more flexible in C#.  Especially since tools like silverlight do
> not allow DllImport's.
> 

Well, browser plugins may have a fun time with git support, but it's so far
from my priority list I couldn't even poke it with a really long pole. The
fastest way forward is probably to hack on libgit2 and use C# micro-apps
to verify continually that the binding layer works properly, so that's what
I'll be doing. I should also state that while C# seems fun and all, my top
priority is to make the git library usable as quickly as possible so that
it can attract more attention from developers. That's why I think it's so
vitally important to get some few usable steps working fast (such as diffing
against the index, staging stuff for commit and creating a commit).

Once we have that much, basic IDE integration should be fairly easy, and
then people will want to do more so interest (hopefully from developers)
is likely to increase.

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

  reply	other threads:[~2008-11-13 11:02 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       ` Andreas Ericsson [this message]
2008-11-13 16:10         ` [MonoDevelop] " 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
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=491C090E.4070605@op5.se \
    --to=ae@op5.se \
    --cc=christian.hergert@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=m.j.hutchinson@gmail.com \
    --cc=monodevelop-list@lists.ximian.com \
    --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).