All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Aguilar <davvid@gmail.com>
To: Jakub Narebski <jnareb@gmail.com>
Cc: Phil Hord <hordp@cisco.com>, "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [RFC] Questions for "Git User's Survey 2011"
Date: Sat, 3 Sep 2011 16:41:12 -0700	[thread overview]
Message-ID: <93869719-D3B6-4D82-824E-1801B9422C3D@gmail.com> (raw)
In-Reply-To: <201109031100.54775.jnareb@gmail.com>

On Sep 3, 2011, at 2:00 AM, Jakub Narebski <jnareb@gmail.com> wrote:

> On Sat, 3 Sep 2011, David Aguilar wrote:
>> On Mon, Jul 25, 2011 at 05:58:32PM -0400, Phil Hord wrote:
>>> On 07/25/2011 04:33 PM, Jakub Narebski wrote:
>>>> === 11. What Git interfaces, implementations and frontends do you use? ===
>>>> (multiple choice, with other)
> [...]
> 
>>> Looking at the 2010 results, I would add these GUIs to the main list:
>>> git-gui (core)
>>> gitk (core)
>>> gitX
>>> gitg
>>> git-cola
>>> TortoiseGit
>>> SmartGit
>>> Git Extensions
>>> Giggle
>> 
>> This is a better list ;-)
> 
> Because of huge number of Git GUIs and tools instead of providing a long
> list of tools to choose from, I went for free-form question:

okay, that makes sense.

nevertheless, we are advertising cogito (deprecated) and pyrite (never made it past pre-alpha in 2008).  why? these should be removed. if you need a replacement, might I suggest git-cola? ;-)I think removing (and thus not advertising) dead tools is more important than coming up with replacements. this is on page 4/10 on the survs.com link you sent elsewhere in this thread.


>  === 13. List git tools that you use (optional) ===
>  (free form, essay)
> 
>  Description:
>  ~~~~~~~~~~~~
>  Please include only frontends, interfaces and tools that have support
>  for Git (so e.g. EGit applies, but Eclipse doesn't).
> 
>  Please either use comma separated list of tools, or put each tool in a
>  separate line.  That would make analysis of answers simpler.  Thanks
>  in advance.
> 
> Even though it is free-form question, it shouldn't be hard to analyse,
> though it wouldn't be completely automatical.
> -- 
> Jakub Narebski
> Poland

  reply	other threads:[~2011-09-03 23:41 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
2011-09-03  8:45   ` David Aguilar
2011-09-03  9:00     ` Jakub Narebski
2011-09-03 23:41       ` David Aguilar [this message]
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=93869719-D3B6-4D82-824E-1801B9422C3D@gmail.com \
    --to=davvid@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=hordp@cisco.com \
    --cc=jnareb@gmail.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.