All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Ericsson <ae@op5.se>
To: JD Guzman <jd@jdguzman.com>
Cc: git@vger.kernel.org
Subject: Re: C# Git Implementation
Date: Sat, 29 Nov 2008 14:44:33 +0100	[thread overview]
Message-ID: <49314741.9090005@op5.se> (raw)
In-Reply-To: <001501c9515e$66e8ac70$34ba0550$@com>

JD Guzman wrote:
> Hello I am new to the list and if I am not following some kind of list
> ettiquite please let me know. 
> 
> I read in the archives that there was once talk of porting Git over to C#
> and was wondering if anything ever came of this?

That depends. I think it's happened at least on three different occasions
that someone wants to port git to C#. The latest is the attempt to write a
libified git (in C) that will be DllImport()'ed from C#, which the devs at
MonoDevelop were sort of interested in. I'm currently working (very slowly)
on libgit2, and it's nowhere near usable today.

>  I realize there were some
> that didn't see the use for this but as Git is becoming more and more
> popular a more native implementation of Git for windows users would be a
> good endevour IMHO.
> 

Truly. However, a better way forward is to create a portable git library
that any old application can use, no matter what language the application
is written in. That way, GUI-hackers can add all the bells and whistles
they like.

Besides that, msysgit works very well on Windows.

> At any rate any info would be greatly appreciated.
> 

libgit2 is available from
http://www.spearce.org/projects/scm/libgit2/libgit2.git
git://git.op5.org/git/libgit2.git

The first URL belongs to Shawn O. Pearce, the initiator of the libgit2
project. The second one is where I stash random stuff that I work on.
Note that git.op5.org is subject to heavy rebasing at the moment, as I'm
basically using it as a patch queue for Shawn (and everyone else who's
interested) to look at when they feel like it. It's not yet interesting
enough to warrant sending everything as patches to git@vger, but a small
bunch of people are helping making the small internal API's reliably
portable (filesystem operations, thread-local error handling) so that
we can nail them down hard to prevent having to change them (and their
hundreds of callers) in the future.

-- 
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-29 13:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-28 13:37 C# Git Implementation JD Guzman
2008-11-28 13:45 ` Reece Dunn
2008-11-29 13:44 ` Andreas Ericsson [this message]
2008-11-29 18:08 ` Asheesh Laroia
2008-11-29 19:27   ` Alejandro Riveira
2008-11-29 19:55   ` Robin Rosenberg
2009-07-11 21:25   ` henon
2009-07-13  0:37     ` Frank Li

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=49314741.9090005@op5.se \
    --to=ae@op5.se \
    --cc=git@vger.kernel.org \
    --cc=jd@jdguzman.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.