git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: [RFC] Questions for "Git User's Survey 2010" - features used, features wanted
Date: Sun, 15 Aug 2010 23:57:28 +0200	[thread overview]
Message-ID: <201008152357.29889.jnareb@gmail.com> (raw)

In the upcoming "Git User's Survey 2010" (tentatively planned to start 
on 1 September 2010) there are two questions about Git features: one 
about features one use, and one about features one would like to see in 
Git.

Below there is excerpt of "Git User's Survey 2010" draft with those 
questions.  Do you have any comments (any features to add, or any 
features to remove in proposed answers in multi-choice) about them?

TIA


-----------

15. Which of the following features do you use?

(multiple choice, with other)

 + git bundle (off-line transport)
 + "smart" HTTP support
 + eol conversion (crlf)
 + custom diff/merge driver
 + textconv
 + gitattributes (other than above)
 + submodules (subprojects)
 + subtree merge (optionally git-subtree)
 + partial (sparse) checkout
 + assume-unchanged bit
 + separate worktree / core.worktree
 + multiple worktrees (git-new-worktree)
 + alternates mechanism (sharing object database)
 + stash (optionally "git stash --keep-index")
 + shallow clone (e.g. "git clone --depth=<n>")
 + detaching HEAD (e.g. "git checkout HEAD^0")
 + interactive rebase (small scale history editing)
 + interactive commit / per-hunk comitting / partial commit
 + commit message templates
 + git-filter-branch or equivalent (large history rewriting)
 + bisect (optionally "git bisect run <script>")
 + committing with dirty tree (keeping some changes uncommitted)
 + non-default hooks (from contrib/hooks/ or other)
 + shell completion of commands
 + git-aware shell prompt
 + git aliases, shell aliases for git, or own git scripts
 + one-way interaction with other SCMs (from SCM to git)
 + two-way interaction with other SCMs (git as fat client)
 + git cvsserver
 + git notes

 + Other, please specify


16. Which of the following features would you like to see implemented
    in git?

(multiple choice)

 + better support for big files (large media)
 + resumable clone/fetch (and other remote operations)
 + GitTorrent Protocol, or git-mirror
 + lazy clone / on-demand fetching of object
 + subtree clone
 + support for tracking empty directories
 + environmental variables in config, expanding ~ and ~user
 + better undo/abort/continue, and for more commands
 + '-n' like option for each command, which describes what would happen
 + warn before/when rewriting published history
 + side-by-side diffs and/or color-words diff in gitweb
 + admin and/or write features in gitweb
 + graphical history view in gitweb
 + GUI for rebase in git-gui
 + GUI for creating repository in git-gui
 + graphical diff/merge tool integrated with git-gui
 + syntax highlighting in git-gui
 + filename encoding (in repository vs in filesystem)
 + git push --create
 + localization of command-line messages (i18n)
 + wholesame directory rename detection
 + union checkouts (some files from one branch, some from other)
 + advisory locking / "this file is being edited"
 + "commands issued" (or "command equivalents") in git-gui / gitk
 + built-in gitjour/bananajour support
 + better support for submodules

 + other (describe below)


17. Describe what features would you like to have in Git, 
    if it is not on the list above?

(free form, essay length)

-- 
Jakub Narebski
Poland

             reply	other threads:[~2010-08-15 21:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-15 21:57 Jakub Narebski [this message]
2010-08-15 22:13 ` [RFC] Questions for "Git User's Survey 2010" - features used, features wanted Jonathan Nieder
2010-08-15 22:51   ` Jakub Narebski
2010-08-16  6:51     ` Matthieu Moy
2010-08-15 23:33 ` Ævar Arnfjörð Bjarmason
2010-08-16  1:54 ` Junio C Hamano

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=201008152357.29889.jnareb@gmail.com \
    --to=jnareb@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.
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).