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

Re: [RFC] Git User's Survey 2007

From
Shawn O. Pearce <spearce@spearce.org>
Date
Jul 30, 2007, 03:35 UTC
Message-ID
<20070730033543.GP20052@spearce.org>
In-Reply-To
<200707300221.23511.jnareb@gmail.com>
Jakub Narebski <jnareb@gmail.com> wrote:
Show 11 quoted lines
> Paolo Ciarrocchi wrote:
> > git-gui ?
> > 
> >>     9. Which git GUI do you use
> >>        (zero or more: multiple choice)
> >>     -  gitk, git-gui, qgit, gitview, giggle, other
>           tig, instaweb, (h)gct, qct, KGit
> 
> I consider git-gui an UI (like qgit or tig), not a porcelain. To be
> a porcelains tool need to add some SCM functionality not present in
> git-core.

Odd. I consider git-gui to be a porcelain, just as I consider tig and qgit to also be porcelain. Though I think git-gui is more of a porcelain than the others, as it tries to rely *less* on the core porcelain and just on the plumbing. I don't always succeed, but I'm heading in that direction.

To me a porcelain is any tool that layers over the plumbing and makes it easier for the end-user to operate it. Early git only had things like read-tree/write-tree/commit-tree. Tying that all up into a neat "Commit" command for the end-user is the job of porcelain.

Anyway. Just so long as git-gui is included in the survey. I'm interested in seeing how many people use it, because I know it has a pretty decently sized userbase. Which is probably going to grow in the future with the i18n work going on.

Do we have any questions in the survey about the user's native language? About their desire to have git translated into their native language? Folks are now working on translating git-gui, and that work will be in git-gui 0.9.x, if not 0.8.1/2. So it may be nice to know what languages our users are interested in.

-- 
Shawn.
Previous: Jakub NarebskiNext: Jakub Narebski
Message 12 of 46 in “Git User's Survey 2007”
  1. Jakub NarebskiJul 25, 2007
  2. Marco CostalbaJul 25, 2007
  3. Steven GrimmJul 26, 2007
  4. [RFC] Git User's Survey 2007Jakub Narebski, Jul 27, 2007
  5. Nguyen Thai Ngoc DuyJul 27, 2007
  6. Andy ParkinsJul 27, 2007
  7. Jakub NarebskiJul 27, 2007
  8. Andy ParkinsJul 28, 2007
  9. Paolo CiarrocchiJul 29, 2007
  10. Paolo CiarrocchiJul 29, 2007
  11. Jakub NarebskiJul 30, 2007
  12. Shawn O. PearceJul 30, 2007
  13. Jakub NarebskiJul 30, 2007
  14. Paolo CiarrocchiJul 30, 2007
  15. Jakub NarebskiJul 30, 2007
  16. David KastrupJul 30, 2007
  17. Junio C HamanoJul 30, 2007
  18. Jakub NarebskiJul 30, 2007
  19. David KastrupJul 30, 2007
  20. Nguyen Thai Ngoc DuyJul 30, 2007
  21. Jakub NarebskiJul 30, 2007
  22. [RFC (take 2) Git User's Survey 2007Jakub Narebski, Jul 30, 2007
  23. Shawn O. PearceJul 31, 2007
  24. Jakub NarebskiJul 31, 2007
  25. Shawn O. PearceJul 31, 2007
  26. Junio C HamanoJul 31, 2007
  27. Shawn O. PearceJul 31, 2007
  28. Jakub NarebskiJul 31, 2007
  29. Paolo CiarrocchiJul 31, 2007
  30. Jakub NarebskiJul 31, 2007
  31. Git User's Survey 2007 - web survey siteJakub Narebski, Jul 31, 2007
  32. Paolo CiarrocchiJul 31, 2007
  33. Martin LanghoffAug 2, 2007
  34. Paolo CiarrocchiAug 2, 2007
  35. [RFC (take 3)] Git User's Survey 2007Jakub Narebski, Aug 4, 2007
  36. Shawn O. PearceAug 4, 2007
  37. Jakub NarebskiAug 4, 2007
  38. David KastrupAug 4, 2007
  39. Jakub NarebskiAug 5, 2007
  40. Johannes SchindelinAug 6, 2007
  41. Asger Ottar AlstrupAug 5, 2007
  42. Jakub NarebskiAug 6, 2007
  43. Asger Ottar AlstrupAug 6, 2007
  44. Jakub NarebskiAug 6, 2007
  45. [RFC (take 4)] Git User's Survey 2007Jakub Narebski, Aug 5, 2007
  46. [RFC (final)] Git User's Survey 2007Jakub Narebski, Aug 14, 2007

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.