git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Richard Hartmann" <richih.mailinglist@gmail.com>
To: git@vger.kernel.org
Subject: Feedback outside of the user survey
Date: Thu, 16 Oct 2008 12:19:36 +0200	[thread overview]
Message-ID: <2d460de70810160319r4bed8643g884508cdeba772@mail.gmail.com> (raw)

Hi all,

unfortunately, I did not know there was a survey, so I did not
participate in it.

I still want to give some feedback from my experiences with
git.
From browsing the results [1] of said survey, I see one
request being made a lot of times. It's basically my main
gripe with git, as well :)

git can do a lot of things, but, as a new user, you are never
quite sure where to start. Docs are geared towards advanced
users (which is fine), but there is no easy entry point (which
is bad).

I would suggest three approaches to fix this:

1) A table/An overview along the lines of "So, you are used to
foo and that is how you do it in git."
For example "What is the equivalent of svn co" (yes, that is an
easy one ;). This should not be limited to things git can do.
svn's ability to pull a subdirectory, which is, ttbomk, lacking
in git, should be included, as well. I am sure there are other
examples [2].

2) A use case repository. "So you want to merge two
branches", etc. This would be a good place to explain the
different ways git offers to do stuff, as well.

3) A tutorial. It does not even have to be as sophisticated
as vimtutor. A simple text file specifying steps to do stuff
would be enough.


Thanks,
Richard

[1] http://www.survs.com/app/2/wo/7OeqmUsbjaDuuaLsOCLeSg/0.0.9.3.3.0.1.3.33.1.7.1
[2] http://www.survs.com/app/2/wo/7OeqmUsbjaDuuaLsOCLeSg/0.0.9.3.3.0.1.3.14.1.7.1

             reply	other threads:[~2008-10-16 10:21 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-16 10:19 Richard Hartmann [this message]
2008-10-16 10:28 ` Feedback outside of the user survey Jeff King
2008-10-16 11:08   ` Richard Hartmann
2008-10-16 11:56 ` Garry Dolley
2008-10-16 13:18   ` Richard Hartmann
2008-10-16 20:32     ` Christian Jaeger
2008-10-18 13:49       ` Garry Dolley
2008-10-18 14:01         ` Christian Jaeger
2008-10-20  9:57           ` Andreas Ericsson
2008-10-20 14:43             ` Christian Jaeger
2008-10-20 15:02               ` Andreas Ericsson
2008-10-20 15:20                 ` Christian Jaeger
2008-10-20 16:11                   ` Andreas Ericsson
2008-10-20 16:57                     ` Christian Jaeger
2008-10-20 17:30                       ` Christian Jaeger
2008-10-20 22:41                       ` Junio C Hamano
2008-10-21  7:24                         ` Christian Jaeger

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=2d460de70810160319r4bed8643g884508cdeba772@mail.gmail.com \
    --to=richih.mailinglist@gmail.com \
    --cc=git@vger.kernel.org \
    /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 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 NNTP newsgroup(s).