All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [RFC] GIT user survey
Date: Thu, 06 Jul 2006 01:09:38 -0400	[thread overview]
Message-ID: <1152162578.10415.59.camel@dv> (raw)
In-Reply-To: <e8e1ea$s5c$1@sea.gmane.org>

On Tue, 2006-07-04 at 17:28 +0200, Jakub Narebski wrote:
> Paolo Ciarrocchi wrote:
> 
> > I was wondering whether it could be a good idea to have a kind of "GIT
> > users survey" when google pointed my eyes to this page:
> > http://www.selenic.com/pipermail/mercurial/2006-April/007513.html
> > 
> > So I modified the content of the survey and published a DRAFT here:
> > http://paolo.ciarrocchi.googlepages.com/GITSurvey
> 
> Could you please add the final version (and of course results) on
> Git Wiki (http://git.or.cz/gitwiki), like original one is on Mercurial
> wiki: http://www.selenic.com/mercurial/wiki/index.cgi/UserSurvey ?
> 
> Thanks in advance
> 
> P.S. I wonder why my Mozilla 1.7.12 sees GITSurvey as binary/octet-stream
> instead of text/plain file...

It's not a Mozilla thing.  It's a server configuration.

$ wget http://paolo.ciarrocchi.googlepages.com/GITSurvey
--00:52:45--  http://paolo.ciarrocchi.googlepages.com/GITSurvey
           => `GITSurvey'
Resolving paolo.ciarrocchi.googlepages.com... 64.233.179.93,
64.233.179.91
Connecting to paolo.ciarrocchi.googlepages.com|64.233.179.93|:80...
connected.
HTTP request sent, awaiting response... 200 OK
Length: 2,078 (2.0K) [application/octet-stream]


Regarding the questions (sorry, I could have missed comments of others):

  What is your preferred language?

Preferred to type or preferred to speak?  There answer is not always the
same, at least for me.

  How did you hear about GIT?

With my own ears.  "How did you learn about GIT" would be better because
many respondents probably _read_ about GIT first.

s/histoty/history
s/porcellains/porcelains/

What is the "history depth"?  How do I measure it?

  Which porcelains do you use?

Which child did you abuse today?  Let's avoid loaded questions.  Some
people are just fine with bare git.

Have you tried to get GIT help from other people?

  Better: Have you asked other people to help you with GIT? 

-- 
Regards,
Pavel Roskin

      reply	other threads:[~2006-07-06  5:09 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-24 16:18 [RFC] GIT user survey Paolo Ciarrocchi
2006-06-24 17:05 ` Randal L. Schwartz
2006-06-24 17:08   ` Paolo Ciarrocchi
2006-06-24 19:54     ` Randal L. Schwartz
2006-06-24 20:04       ` Petr Baudis
2006-06-24 20:52         ` Linus Torvalds
2006-06-24 22:09           ` Petr Baudis
2006-06-24 21:55 ` Adrien Beau
2006-06-24 22:15   ` Matthias Kestenholz
2006-06-29  9:49     ` Jakub Narebski
2006-06-24 23:42 ` Martin Langhoff
2006-06-25 10:47   ` Paolo Ciarrocchi
2006-06-25 11:06     ` Junio C Hamano
2006-06-25 14:04       ` Paolo Ciarrocchi
2006-06-25 16:20     ` Sam Ravnborg
2006-07-04 15:28 ` Jakub Narebski
2006-07-06  5:09   ` Pavel Roskin [this message]

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=1152162578.10415.59.camel@dv \
    --to=proski@gnu.org \
    --cc=git@vger.kernel.org \
    --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.