git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[RFC] Questions for "Git User's Survey 2010" - features used, features wanted

From
Jakub Narebski <jnareb@gmail.com>
Date
Aug 15, 2010, 21:57 UTC
Message-ID
<201008152357.29889.jnareb@gmail.com>

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
Next: Jonathan Nieder
Message 1 of 6 in “[RFC] Questions for "Git User's Survey 2010" - features used, features wanted”
  1. Jakub NarebskiAug 15, 2010
  2. Jonathan NiederAug 15, 2010
  3. Jakub NarebskiAug 15, 2010
  4. Matthieu MoyAug 16, 2010
  5. Ævar Arnfjörð BjarmasonAug 15, 2010
  6. Junio C HamanoAug 16, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.