From: Boaz Harrosh <bharrosh@panasas.com>
To: "Frank Münnich" <git@frank-muennich.com>
Cc: git@vger.kernel.org
Subject: Re: What IDEs are you using to develop git?
Date: Tue, 25 Aug 2009 15:56:06 +0300 [thread overview]
Message-ID: <4A93DF66.4080902@panasas.com> (raw)
In-Reply-To: <000001ca257d$b60326c0$22097440$@com>
On 08/25/2009 03:15 PM, Frank Münnich wrote:
> Hi there,
>
> I am interested in helping out and improving git, though I haven't
> programmed in C for quite a while now and thus have to relearn quite some
> things.
> I understand the different branches (master, next, pu) and so on, and were
> successful in compiling git with my Ubuntu 9.04. [yeea] ;)
>
> One thing I would like to ask you: what, if any, IDEs are you working with?
> I tried Anjuta but were unsuccessful in importing the git folder from any
> branch into Anjuta. Eclipse worked a bit better, though I am still batteling
> with the debugger a bit.
>
> Any recommendations, manuals or how-to tips are greatly welcome.
> And one thing: thank you for your effort! Git really caught my attention and
> I was so much amused by the Google-Techtalk that Linus gave about Git, that
> it sparked my interest in relearning how to program again ;)
>
> Best regards from lovely Dresden in Germany
> Frank Münnich
>
kdevelop rocks. Debugging perfect. Just configure a C external-make project
and off you go.
Cheers
Boaz
next prev parent reply other threads:[~2009-08-25 12:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-25 12:15 What IDEs are you using to develop git? Frank Münnich
2009-08-25 12:47 ` John Tapsell
2009-08-30 18:07 ` Daniele Segato
2009-08-30 19:01 ` Nicolas Pitre
2009-08-30 19:06 ` Howard Miller
2009-08-31 10:21 ` Martin Langhoff
2009-08-30 21:29 ` Robin Rosenberg
2009-08-31 8:29 ` Erik Faye-Lund
2009-08-31 8:11 ` Andreas Ericsson
2009-08-31 11:36 ` Rustom Mody
2009-08-25 12:49 ` Andreas Ericsson
2009-08-25 12:56 ` Boaz Harrosh [this message]
2009-08-25 14:06 ` Thell Fowler
2009-08-25 14:18 ` Jakub Narebski
2009-08-26 4:24 ` Jeremy O'Brien
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=4A93DF66.4080902@panasas.com \
--to=bharrosh@panasas.com \
--cc=git@frank-muennich.com \
--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 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.