git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: Phil Hord <hordp@cisco.com>, git@vger.kernel.org
Subject: Re: [RFC] Questions for "Git User's Survey 2011"
Date: Mon, 1 Aug 2011 22:57:43 +0200	[thread overview]
Message-ID: <201108012257.44495.jnareb@gmail.com> (raw)
In-Reply-To: <CAMP44s3y0GX6ofa6Am-ioDyf9AEjKJofsHQLU0L9P4nnQ4C+4w@mail.gmail.com>

On Sun, 31 Jul 2011, Felipe Contreras wrote:
> 2011/7/26 Phil Hord <hordp@cisco.com>:
>> On 07/26/2011 06:37 AM, Jakub Narebski wrote:
>>> On Mon, 25 Jul 2011, Phil Hord wrote:

>>>> IDE integration (Eclipse, Netbeans, etc.)
>>>
>>> This isn't strictly _git_ feature, and is in "12. What kind of Git tools
>>> do you use?" anyway.
>>>
>> Yes, it's not a git feature.  But I'm curious how successful any IDE
>> integration is (as opposed to a GUI, for example).  I haven't seen any
>> that use enough of the power of git yet, so I have been disappointed.  I
>> suspect others have also, but I'm hopeful.
> 
> I also think this is important, in my blog I've seen a bunch of people
> mentioning that Git's integration with IDE's is not as good as
> Mercurial. Putting this in the already existing list of tools would
> not cover missing IDE's being integrated, I think this should go into
> "20. In your opinion, which areas in Git need improvement?"

I think this is a good idea, though perhaps not in question about Git
(it is "which areas in _Git_"), but in a separate question about Git
tools.

 21. In your opinion, what Git tools are needed, and which need improvements?

Or something like that.
-- 
Jakub Narebski
Poland

  reply	other threads:[~2011-08-01 20:57 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-25 20:33 [RFC] Questions for "Git User's Survey 2011" Jakub Narebski
2011-07-25 21:58 ` Phil Hord
2011-07-26 10:37   ` Jakub Narebski
2011-07-26 12:14     ` Phil Hord
2011-07-31 13:37       ` Felipe Contreras
2011-08-01 20:57         ` Jakub Narebski [this message]
2011-09-03  8:45   ` David Aguilar
2011-09-03  9:00     ` Jakub Narebski
2011-09-03 23:41       ` David Aguilar
2011-07-31 13:53 ` Felipe Contreras
2011-08-02 13:37   ` Jakub Narebski
2011-08-01 23:43 ` Heiko Voigt
2011-08-02 11:41   ` Jakub Narebski
2011-08-02 18:52 ` Jens Lehmann
2011-08-03 11:27   ` Jakub Narebski
2011-08-03 16:40 ` Ævar Arnfjörð Bjarmason
2011-08-03 17:40   ` Jakub Narębski
2011-09-03 12:58 ` Felipe Contreras
2011-09-03 15:38   ` Jakub Narebski
2011-09-14 16:14     ` Felipe Contreras
2011-09-14 17:39       ` Jakub Narebski
2012-09-19 17:35         ` Felipe Contreras
2012-09-22 22:45           ` Jakub Narębski
2012-09-23  8:09             ` Junio C Hamano
2012-09-23  9:47               ` Jakub Narębski
2012-09-24 13:23             ` Michael J Gruber
2012-09-24 14:31               ` Jakub Narębski
2012-09-24 15:37             ` Matthieu Moy
2012-09-24 16:11               ` Jakub Narębski
2012-09-24 16:18                 ` Matthieu Moy
2012-09-24 16:23                   ` Jakub Narębski
2012-09-24 19:35                     ` Matthieu Moy
2012-09-24 19:43                       ` Jakub Narębski
2012-09-25  6:17                         ` Matthieu Moy
     [not found]                           ` <CANQwDweD-OSDKkA9P1FPr4jhvv2su5W86J+P8BRV8MmEBgC8BA@mail.gmail.com>
2012-09-25  6:57                             ` Jakub Narębski

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=201108012257.44495.jnareb@gmail.com \
    --to=jnareb@gmail.com \
    --cc=felipe.contreras@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=hordp@cisco.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 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).