git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: "Jörg W Mittag" <Joerg.Mittag@Web.De>
Cc: git@vger.kernel.org
Subject: Re: Why I love GIT but use Subversion
Date: Mon, 31 Jul 2006 21:42:14 -0700	[thread overview]
Message-ID: <7virld2hjt.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <1prv3rw6ldo9s$.dlg@jwmittag.my-fqdn.de> (Jörg W. Mittag's message of "Tue, 1 Aug 2006 03:45:52 +0200")

Jörg W Mittag <Joerg.Mittag@Web.De> writes:

> Please, make those reasons go away.

These are all reasonable wishes.

The core level of git (which is written in C) is designed to be
usable as a building block for platform native IDE.  The primary
audience of git so far has been POSIX envirnoment, and the
command line interface we have in core git was one acceptable
form of "platform native IDE".  I know that is not a usual form
of IDE in some other world (most notably in MS circles).

I do not speak for others on this mailing list, but given the
background of how git came about into existence, which pretty
much defines the majority of the habitants of this mailing list,
I doubt there are many people who know git well enough and have
enough experience and motivation to implement "platform native
IDE" for MS platform.  Certainly I cannot imagine Linus and/or
myself doing Windows GUI programming to make git integrate into
MS environment seamlessly.  You probably are a lot more familiar
and qualified to implement such than myself.

So please step forward, enlist MS comrades, and start hacking,
if you want MS native git.  If you need help in understanding
the core git data structures, algorithms, and functions, I may
well be able to help you.  If you have difficulties interfacing
with Visual Studio on the other hand that is not something I can
help you with, although some others on the list might.

> Thank you for bearing with me through this long rant.

Thank *you* for sharing these thoughts.

  parent reply	other threads:[~2006-08-01  4:42 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-23  8:23 GIT user survey Paolo Ciarrocchi
2006-07-23  8:45 ` Paolo Ciarrocchi
2006-07-23 13:18   ` Jakub Narebski
2006-07-24 13:21     ` Paolo Ciarrocchi
2006-07-24 19:47   ` Wolfgang Denk
2006-07-24 19:50     ` Paolo Ciarrocchi
2006-07-24 20:11       ` Wolfgang Denk
2006-07-24 20:15         ` Paolo Ciarrocchi
2006-07-30  9:48 ` Paolo Ciarrocchi
2006-08-01  1:45   ` Why I love GIT but use Subversion (was: GIT user survey) Jörg W Mittag
2006-08-01  3:50     ` Pavel Roskin
2006-08-01  4:42     ` Junio C Hamano [this message]
2006-08-01  5:39       ` Why I love GIT but use Subversion Martin Langhoff
2006-08-01  7:13     ` Jakub Narebski
2006-08-01 10:13     ` Why I love GIT but use Subversion (was: GIT user survey) Johannes Schindelin
2006-08-01 10:59       ` Martin Langhoff
2006-08-01 12:14         ` Why I love GIT but use Subversion Noel Grandin
2006-08-01 12:46       ` Why I love GIT but use Subversion (was: GIT user survey) Alex Riesen
2006-08-11 15:12 ` GIT user survey Jakub Narebski
2006-08-12 12:24   ` Paolo Ciarrocchi

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=7virld2hjt.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=Joerg.Mittag@Web.De \
    --cc=git@vger.kernel.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).