git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Andrew Ardill <andrew.ardill@gmail.com>
To: "Jakub Narębski" <jnareb@gmail.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>,
	Doug Rathbone <doug@dougrathbone.com>,
	David Bainbridge <david.bainbridge@gmail.com>,
	Stefan Beller <sbeller@google.com>
Subject: Re: [RFC] Proposed questions for "Git User's Survey 2016"
Date: Mon, 22 Aug 2016 09:59:34 +1000	[thread overview]
Message-ID: <CAH5451n0=kmr9SeOKSH5iiJr5Lnr2TapfZrTUR6Pm90xUEKFxQ@mail.gmail.com> (raw)
In-Reply-To: <91a2ffbe-a73b-fbb9-96da-9aea4d439e5a@gmail.com>

On 21 August 2016 at 04:56, Jakub Narębski <jnareb@gmail.com> wrote:
> 25. What [channel(s)] do you use to request/get help about Git [(if any)]

It may also be useful to ask how people hear news about git, such as
when a new release comes out. Not sure if worth a separate question,
as there is a lot of crossover in the resources available for this and
for requesting help, but knowing this information would help us
understand what kinds of users are responding and which communication
channels are effective for git news.

Related, it might be worth asking how often people upgrade their git
clients and servers, particularly in corporate/managed environments.
This question would ask two things, how long after a new release comes
out do you install it, and do you install every update that comes out
or do you skip versions. I suspect many would just use whatever is
released in their distro and update at the same time as they update
other packages, but it would be interesting to know if people, for
example, only upgrade their managed environments every year/6 months
or something to avoid introducing changes to their users.

Regards,

Andrew Ardill

  parent reply	other threads:[~2016-08-22  0:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-20 18:56 [RFC] Proposed questions for "Git User's Survey 2016" Jakub Narębski
2016-08-20 21:29 ` Eric Wong
2016-08-25 10:26   ` Jakub Narębski
2016-08-21 23:59 ` Andrew Ardill [this message]
2016-08-25 14:53   ` Jakub Narębski
2016-08-26  6:58     ` Andrew Ardill
2016-08-26 11:42       ` Jakub Narębski
2016-08-26  6:15 ` Eric Wong
2016-08-26 11:52   ` Jakub Narębski
     [not found]     ` <CAFO0PHfy_teFFMiuFdjKYohCgRZHNT+Cc8hXOjsPeRTi9gAHPQ@mail.gmail.com>
2016-08-26 23:46       ` Jakub Narębski
2016-08-28  9:49     ` Eric Wong
2016-08-28 11:22       ` Jakub Narębski
2016-08-27 22:00 ` [RFCv2] Proposed questions for "Git User's Survey 2016", take two Jakub Narębski
2016-09-05 21:27   ` [RFCv3] Proposed questions for "Git User's Survey 2016", take three Jakub Narębski
     [not found]     ` <CAFO0PHc48OmWNcRrh2Wu30L6Oarqyw+co+zNPpsPEWerCiqanw@mail.gmail.com>
     [not found]       ` <CAFO0PHdGppfgSSYW4YB-0LEsuohyzSCkrk48fovppNfDYZx78w@mail.gmail.com>
2016-09-09 20:20         ` 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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAH5451n0=kmr9SeOKSH5iiJr5Lnr2TapfZrTUR6Pm90xUEKFxQ@mail.gmail.com' \
    --to=andrew.ardill@gmail.com \
    --cc=david.bainbridge@gmail.com \
    --cc=doug@dougrathbone.com \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    --cc=sbeller@google.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).