From: Jakub Narebski <jnareb@gmail.com>
To: Yann Dirson <ydirson@free.fr>
Cc: git@vger.kernel.org
Subject: Re: [RFC] Git User's Survey 2010 (resend)
Date: Wed, 07 Jul 2010 14:43:16 -0700 (PDT) [thread overview]
Message-ID: <m3fwzvm0jc.fsf@localhost.localdomain> (raw)
In-Reply-To: <loom.20100707T105938-93@post.gmane.org>
Yann Dirson <ydirson@free.fr> writes:
> Jakub Narebski <jnareb <at> gmail.com> writes:
> > === xx. Have you found distributed version control easy? ===
> > (multiple choice)
> >
> > + Very easy
> > + Easy
> > + Reasonably easy
> > + Hard
> > + Very hard
> >
> > Or something like that, with separate question if DVCS is difficult
> > or not.
> >
> > Alternatively we could ask about _relative_ ease of learning / use.
> > But I don't think this would go well (and I don't think we could get
> > good answers from that).
>
> Related to that, would be whether the user was familiar with DVCS before
> starting to use git, or even familiar with VCS - the answers would be different
> for people for whom git is the first VCS they ever used, or for people having
> used other DVCS before...
Relative ease of use of Git as compared to perceived ease of
distributed version control as generic subject.
But I don't think it is a good way to go (and get meaningfull
answers).
> > Well, Git User's Surveys always served more or less accidentally as
> > the source of information about git and git community ("we have wiki?"
> > from the first survey )
>
> Count me in for "we have git new-worktree ?" :)
> In fact, I found nothing by that name in git's tree or in the wiki's
> InterfacesFrontendsAndTools. Google finally pointed me to contrib/ where I
> noticed workdir/git-new-workdir.
>
> It may be worth to use a URL for publicizing non-mainstream stuff. That's
> better as publicizing goes, and makes it easy to crowdsource discovery of
> mistakes or outdated things.
Hmmm... perhaps it would be worth to create GitContrib page on Git
Wiki, and link it from InterfacesFrontendsAndTools page...
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2010-07-07 21:43 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-03 19:58 [RFC] Git User's Survey 2010 (resend) Jakub Narebski
2010-07-04 0:21 ` Ævar Arnfjörð Bjarmason
2010-07-04 8:13 ` Jakub Narebski
2010-07-07 9:18 ` Yann Dirson
2010-07-07 21:43 ` Jakub Narebski [this message]
2010-07-10 11:01 ` Felipe Contreras
2010-07-04 9:07 ` David Bainbridge
2010-07-04 11:14 ` Jakub Narebski
2010-07-04 20:48 ` David Bainbridge
2010-07-05 7:19 ` Jakub Narebski
2010-07-04 22:43 ` Scott Chacon
2010-07-04 23:48 ` Jakub Narebski
2010-07-07 12:28 ` Yann Dirson
2010-07-07 21:37 ` Jakub Narebski
2010-07-08 7:24 ` Yann Dirson
2010-07-10 11:31 ` Felipe Contreras
2010-07-10 19:58 ` Jakub Narebski
2010-07-11 9:57 ` Felipe Contreras
2010-07-11 17:42 ` Jakub Narebski
2010-07-12 10:14 ` David Bainbridge
2010-07-12 10:19 ` Felipe Contreras
2010-07-12 10:22 ` David Bainbridge
2010-08-09 21:59 ` Felipe Contreras
2010-08-10 22:16 ` Jakub Narebski
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=m3fwzvm0jc.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=ydirson@free.fr \
/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).