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

Re: [RFC v2] Git User's Survey 2008

From
Jakub Narebski <jnareb@gmail.com>
Date
Aug 22, 2008, 00:06 UTC
Message-ID
<200808220206.59694.jnareb@gmail.com>
In-Reply-To
<20080821212620.GA9718@leksak.fem-net>
Stephan Beyer wrote:
> Jakub Narebski wrote:
Show 9 quoted lines
> > > This question leads me to a question that could be put into the survey:
> > > 
> > > 	Where have you read about this survey? (optional)
> > > 	[Free form]
> > 
> > But where to add it?  Additionally I'd rather limit free-form questions
> > to absolute minimum.
> 
> If you want to add it nonetheless, then it could be question 60.

I'll added it. It would be useful if there would be survey in the following years.

Show 12 quoted lines
> > > > What other SCM did or do you use?
> > > >[..]
> > > >  custom ( ) ( ) ( )
> > > 
> > > custom?
> > 
> > I mean here custom, not published (or no longer existing) SCM; something
> > that would be hard to write about.
> 
> This means the difference to "other" is that it is something somebody
> has written for herself (or a company product only used in that
> company) and "other" is some less popular but public SCM?
Yes.
> I see you've changed it to "custom (non published)". There is a typo:
> s/non /non-/  ;)
Thanks, corrected and added explanation below the question.
 
[...]
Show 5 quoted lines
> > But it is here for completeness only; however if you have some good
> > explanation for "core-git" option I can put it below this question.
> 
> I think it should be rephrased by "git" or "git (pure)" or "git (core)".
> But "core-git" really looks like another tool to me.
Done.
Show 13 quoted lines
> > > > (*) Unless of cours you are hosting some git hosting site
> > >              ^^^^^^^^                                      ^
> > > 	     typo, but I'd rather do s/of cours //   and s/$/./ :-)
> > 
> > Thanks.  Done.
> 
> Now it is:
> > (*) Unless of course you are hosting some git hosting site
>             ^         ^                                     ^
> I like punctuation:
>   (*) Unless, of course, you are hosting some git hosting site.
> 
> *nitpick* :-)
Done.
Show 23 quoted lines
> > > > 28. Which of the following features do or did you use?
> > > 
> > > I think many of the possible replies have been used in several other
> > > questions before, e.g. in 
> > >  - 21. (gitk, git gui), 
> > >  - 24. (git bundle),
> > >  - 26/27. (git gui, gitk, git stash)
> > >  - ...
> > > 
> > > But this question still seems to makes sense for:
> > >  [ ] eol conversion (crlf)
> > >  [ ] gitattributes
> > >  [ ] reflog (ref@{23})
> > >  [ ] shallow clone
> > >  [ ] detaching HEAD   <- I think several people could have used that without knowing
> > >  [ ] commit templates
> > >  [ ] integration with IDE/editor
> > >  [ ] non-default hooks
> 
> No comment here? ;-)
> 
> When replying to this question I really felt like having answered all
> that before.

They _are_ different questions; yes, some answers repeat themselves because I tried each question to be self-contained, if possible, so it should be easy to skip some question and still have full value in the rest of questions.

Show 10 quoted lines
> > > And btw:
> > > > [ ] working with dirty tree      <- Eh? Is this a feature?
> > 
> > This is distinguishing feature.  What I mean here that you can use
> > "git add" and "git commit" (not "git commit -a")
> 
> Sounds like "Taking advantage of using the index".
> (Yesterday/today/tomorrow I am using SVN in university and I wished so
> much that I had some git or at least git-svn[1] just because of the
> *index*.)

Hmmm... reading the above I have thought about adding "incremental committing" to the list of features; I mean here the workflow of "<edit>; git add; git diff/git diff --cached; <edit>; git add; commit"

But I think I'll just add "the index" to question
  30. Which features do you find unique and/or useful ones,
      compared to other systems (other SCMs)?

and leave the rest for free-form question 31. following it: "If you use some important Git features not mentioned above, what are those?".

> Another general comment: Multiple choice question have the disadvantage
> that we cannot distinguish "None" and skipped questions.
> So if this is an issue, I wonder if adding a "None of the above" choice
> could help. But perhaps this is no issue and can be ignored.
Hmmmm....
-- 
Jakub Narebski
Poland
Previous: Stephan BeyerNext: Mike Gant
Message 80 of 93 in “[RFC] Git User's Survey 2008”
  1. Jakub NarebskiJul 23, 2008
  2. Junio C HamanoJul 23, 2008
  3. HP-UX issues (WAS: Re: [RFC] Git User's Survey 2008)Miklos Vajna, Jul 23, 2008
  4. Jakub NarebskiJul 23, 2008
  5. Miklos VajnaJul 23, 2008
  6. Jakub NarebskiJul 23, 2008
  7. Marek ZawirskiJul 24, 2008
  8. Mailing lists, was Re: [RFC] Git User's Survey 2008Johannes Schindelin, Jul 24, 2008
  9. Shawn O. PearceJul 25, 2008
  10. Junio C HamanoJul 25, 2008
  11. Jakub NarebskiJul 25, 2008
  12. Shawn O. PearceJul 25, 2008
  13. Junio C HamanoJul 25, 2008
  14. Shawn O. PearceJul 25, 2008
  15. Jakub NarebskiJul 26, 2008
  16. Marek ZawirskiJul 26, 2008
  17. Shawn O. PearceJul 26, 2008
  18. Jean-François VeilletteJul 26, 2008
  19. Petr BaudisJul 25, 2008
  20. Jing XueJul 26, 2008
  21. Jakub NarebskiJul 26, 2008
  22. Shawn O. PearceJul 26, 2008
  23. Jakub NarebskiJul 26, 2008
  24. Johannes SchindelinJul 26, 2008
  25. Scott ChaconJul 26, 2008
  26. Jakub NarebskiJul 24, 2008
  27. Johannes SchindelinJul 23, 2008
  28. Jakub NarebskiJul 23, 2008
  29. Johannes SchindelinJul 23, 2008
  30. Robin RosenbergJul 23, 2008
  31. Johannes SchindelinJul 23, 2008
  32. Jakub NarebskiJul 24, 2008
  33. Jakub NarebskiJul 23, 2008
  34. Johannes SchindelinJul 23, 2008
  35. Stephan BeyerJul 23, 2008
  36. david@lang.hmJul 24, 2008
  37. Stephan BeyerJul 24, 2008
  38. david@lang.hmJul 24, 2008
  39. Jakub NarebskiJul 24, 2008
  40. Jakub NarebskiJul 26, 2008
  41. Nguyen Thai Ngoc DuyJul 27, 2008
  42. Junio C HamanoJul 23, 2008
  43. Jakub NarebskiJul 24, 2008
  44. Dmitry PotapovJul 23, 2008
  45. Johannes SchindelinJul 23, 2008
  46. Stephan BeyerJul 23, 2008
  47. Jakub NarebskiJul 24, 2008
  48. Alex RiesenJul 23, 2008
  49. Jakub NarebskiJul 24, 2008
  50. Stephan BeyerJul 23, 2008
  51. Stephan BeyerJul 24, 2008
  52. Dmitry PotapovJul 23, 2008
  53. Matthias KestenholzJul 23, 2008
  54. Dmitry PotapovJul 23, 2008
  55. Jakub NarebskiJul 23, 2008
  56. Dmitry PotapovJul 24, 2008
  57. Jakub NarebskiJul 24, 2008
  58. Petr BaudisJul 23, 2008
  59. Jakub NarebskiJul 23, 2008
  60. Jon LoeligerJul 24, 2008
  61. Jakub NarebskiJul 24, 2008
  62. Lachele Foley (Lists)Jul 24, 2008
  63. Jakub NarebskiJul 24, 2008
  64. Dmitry PotapovJul 24, 2008
  65. Jakub NarebskiJul 24, 2008
  66. Jakub NarebskiJul 31, 2008
  67. [RFC v2] Git User's Survey 2008Jakub Narebski, Aug 20, 2008
  68. Alex RiesenAug 20, 2008
  69. Petr BaudisAug 20, 2008
  70. Jakub NarebskiAug 20, 2008
  71. Alex RiesenAug 20, 2008
  72. Junio C HamanoAug 20, 2008
  73. Jakub NarebskiAug 21, 2008
  74. Junio C HamanoAug 21, 2008
  75. Jakub NarebskiAug 21, 2008
  76. Stephan BeyerAug 20, 2008
  77. Stephan BeyerAug 20, 2008
  78. Jakub NarebskiAug 21, 2008
  79. Stephan BeyerAug 21, 2008
  80. Jakub NarebskiAug 22, 2008
  81. Mike GantAug 21, 2008
  82. Stephan BeyerAug 24, 2008
  83. Jakub NarebskiAug 25, 2008
  84. Abhijit BhopatkarAug 20, 2008
  85. [RFC v3] Git User's Survey 2008Jakub Narebski, Aug 25, 2008
  86. Stephan BeyerAug 28, 2008
  87. [RFC v4] Git User's Survey 2008 (cover letters)Jakub Narebski, Aug 30, 2008
  88. Garry DolleyAug 30, 2008
  89. Paolo CiarrocchiSep 1, 2008
  90. Miguel ArrozJul 23, 2008
  91. Jakub NarebskiJul 23, 2008
  92. Sverre RabbelierJul 24, 2008
  93. Jakub NarebskiAug 25, 2008

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.