All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: Phil Hord <hordp@cisco.com>
Cc: git@vger.kernel.org
Subject: Re: [RFC] Questions for "Git User's Survey 2011"
Date: Tue, 26 Jul 2011 12:37:42 +0200	[thread overview]
Message-ID: <201107261237.43140.jnareb@gmail.com> (raw)
In-Reply-To: <4E2DE708.8050805@cisco.com>

On Mon, 25 Jul 2011, Phil Hord wrote:
> On 07/25/2011 04:33 PM, Jakub Narebski wrote:

> > NOTES:
> > ^^^^^^
> > How to detect if it is msysGit or Cygwin from within?  Perhaps we
> > should have just "MS Windows"...
> 
> I think it's useful to know which build they're using, cygwin or msys. 
> Hopefully it's not too confusing for them and they can answer correctly.

Well, there is this option for those confused:

 + some MS Windows (unknown or other)

I should probably add

 + operating system independent (JGit, Dulwich, git.js, ...)
 
> > === 11. What Git interfaces, implementations and frontends do you use? ===
> > (multiple choice, with other)
> >
> >  + JGit (Java implementation), e.g. via Eclipse plugin
> >  + NGit or Git# (C# implementation)
> >  + Dulwich (pure-Python implementation)
> >  + Git::PurePerl (Perl implementation)
> >  + git.js (JavaScript)
> >  + libgit2 bindings
> >
> >  + git (core) commandline
> >  + Cogito (DEPRECATED)
> >  + Easy Git
> >  + Pyrite
> >  + I don't know, I only use (graphical) tools
> >
> >  + pg aka Patchy Git (DEPRECATED)
> >  + StGIT
> >  + Guilt
> >  + TopGit
> >
> >  + Zit
> >
> >  + other (please specify)
> 
> You can probably drop pg and Cogito now, yes?

Yes, I think they can be dropped now.  They were important in previous
years to check if people are still using those deprecated porcelains,
but nowadays I don't think it is necessary.
 
> 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

Hmmm... they can be considered "frontends", but there are too many GUIs
there to add them all.  They are in a way in "12. What kind of Git tools
do you use?"

Perhaps it would be good idea to add free-form (because of sheer number
of git tools) to write git tools etc. that one uses.
 
> Is there room for Gerrit here, or maybe in one of the other questions?
> Also, cgit and other web interfaces, I suppose.

They are in "12. What kind of Git tools do you use?".

> > === 16. Which of the following Git features do you use? ===
> > (multiple choice, with other)
> >
> >  + localization of command-line messages (i18n)
> >  + git bundle (off-line transport)
[...]
> >  + one-way interaction with other SCMs (from SCM to git)
> >  + two-way interaction with other SCMs (from SCM to git, from git to SCM)
> >
> >  + git-cvsserver
> >  + git notes
> >
> >
> >  + Other, please specify
> >
> > NOTES:
> > ^^^^^^
> > The problem is come up not with exhaustive list of features: there are
> > too many of them to list.  The problem is coming up with list of
> > important and used enough often features.
> >
> > So: what features should be included in this list?  What features
> > should be removed from above list of answers?
> 
> bridges (git-svn, hg-git, git-p4, etc.)

I think they are included in "two-way interaction with other SCMs",
but perhaps that should be made more clear.

> IDE integration (Eclipse, Netbeans, etc.)

This isn't strictly _git_ feature, and is in "12. What kind of Git tools
do you use?" anyway.


Thank you very much for your comments.
-- 
Jakub Narebski
Poland

  reply	other threads:[~2011-07-26 10:37 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 [this message]
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
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=201107261237.43140.jnareb@gmail.com \
    --to=jnareb@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 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.