From: "Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
To: git@vger.kernel.org
Subject: Re: Git Survey summary
Date: Thu, 21 Sep 2006 21:12:18 +0700 [thread overview]
Message-ID: <fcaeb9bf0609210712i125822c4gf8af3ecccdbd3d13@mail.gmail.com> (raw)
In-Reply-To: <fcaeb9bf0609120205m38a44571we21e05864c04a731@mail.gmail.com>
FYI, I've completed the survey summary (except Q13, repo size, which I
don't know how to handle it. And there was no Q14 in GitSurveyData).
You may be interested in Q20 and Q31.
Some thought after completing this summary:
- Documentation is still most wanted (as a comprehensive book or
examples/use-cases). There were many answers indicated that users
didn't know about existing git features. We should advertise git
features more.
- Git homepage and Git wiki (and sometimes git mailing list) are
unknown to many users. Perhaps we should put them in git.7 man page?
- Plumbings/Porcelains confustion. Is it about time to move all git-*
into /usr/lib/git? Also some probably wants to integrate cogito into
git.
- A place to post bugs and feature requests (if bugzilla is too big,
maybe mantis?)
- (This comment is mine) Git should ship NEWS file in release
tarballs. An auto generated ChangeLog in tarballs is also great (maybe
make git-changelog to generate the changelog)
--
Duy
next prev parent reply other threads:[~2006-09-21 14:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-12 9:05 Git Survey summary Nguyễn Thái Ngọc Duy
2006-09-21 14:12 ` Nguyễn Thái Ngọc Duy [this message]
2006-09-21 15:23 ` Jakub Narebski
2006-09-21 15:56 ` Shawn Pearce
2006-09-21 16:13 ` Jakub Narebski
2006-09-21 16:27 ` Shawn Pearce
2006-09-21 16:34 ` Petr Baudis
2006-09-21 16:49 ` Jakub Narebski
2006-09-21 16:44 ` Jakub Narebski
2006-09-21 16:37 ` Petr Baudis
2006-09-21 16:48 ` Shawn Pearce
2006-09-21 16:49 ` Nguyen Thai Ngoc Duy
2006-09-21 17:00 ` Petr Baudis
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=fcaeb9bf0609210712i125822c4gf8af3ecccdbd3d13@mail.gmail.com \
--to=pclouds@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).