git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Ericsson <ae@op5.se>
To: Git Mailing List <git@vger.kernel.org>,
	Shawn Pearce <spearce@spearce.org>,
	Michael Hutchinson <m.j.hutchinson@gmail.com>
Subject: Re: git integration with monodevelop
Date: Wed, 12 Nov 2008 11:31:20 +0100	[thread overview]
Message-ID: <491AB078.6020208@op5.se> (raw)
In-Reply-To: <491AAE6D.8030304@op5.se>

Andreas Ericsson wrote:
> Recently, I've started learning C#. More for fun than anything else,
> but one of the mono core devs sniffed me out and said they've been
> thinking of porting jgit to C# to get a working IDE integration in
> monodevelop. Currently, the only option available (with IDE
> integration anyways) to the poor C# devs is either Microsoft's
> crappy VSS, or the less crappy but still far from fantastic
> Subversion.
> 
> So in an effort to learn C#, I've decided to play along with this
> (hopefully with some help from the MonoDevelop team), but it seems
> to me that the best place to start is the fledgling libgit2 and link
> that with git-sharp. The primary reason for this is ofcourse that I
> think it'd be a terrible waste to have yet another from-scratch
> implementation of git in a new language (ruby, java, C#, C...). The
> secondary reason is that it would be neat to have more OSS projects
> use my favourite scm.
> 
> Besides, getting something to rely on libgit2 early on is probably
> the best way to get more people interested in making development of
> it proceed rapidly.
> 
> Thoughts anyone?
> 
> Please reply-to-all as this goes cross-list
> (currently, Cc ae@op5.se, spearce@spearce.org, git@vger.kernel.org,
> m.j.hutchinson@gmail.com, in case monodevelop-list uses reply-to
> header).
> 

Ouch. Scratch monodevelop-list from that Cc list. It appears to be
members-only (although not listed as such on their list-server).

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

  reply	other threads:[~2008-11-12 10:32 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 [this message]
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
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=491AB078.6020208@op5.se \
    --to=ae@op5.se \
    --cc=git@vger.kernel.org \
    --cc=m.j.hutchinson@gmail.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).