From: Jakub Narebski <jnareb@gmail.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: git@vger.kernel.org
Subject: Re: [RFC (take 3)] Git User's Survey 2007
Date: Sat, 4 Aug 2007 14:10:21 +0200 [thread overview]
Message-ID: <200708041410.22449.jnareb@gmail.com> (raw)
In-Reply-To: <20070804054157.GN20052@spearce.org>
On Sat, 4 August 2007, Shawn O. Pearce wrote:
>> How you use GIT
>>
>> 1. Do you use GIT for work, unpaid projects, or both?
>> work/unpaid projects/both/none(*)
>> (*)I use git to interact with some project I'm interested in
>
> I don't understand the (*) point here. What's the middle ground
> between work and unpaid projects? Paid projects that aren't work?
> Isn't that the definition of work? Very confused...
I meant here to add an option for people who use git (or git web
interface) only for tracking some project(s). For example what if I'm
tracking git.git repository, but do not have repositories with my own
projects? It is a bit of gray area if you publish your own changes to
somebody else project if it is "none" or "unpaid projects".
But perhaps it is too vague distinction. One can always not to answer
this question, if one does not have any projects, and do not use git
for work.
I'll think about removing this option.
>> 8. Which porcelains do you use?
>> (zero or more: multiple choice)
>> - core-git, cogito, StGIT, pg, guilt, other
>
> I really hope nobody chooses pg. I haven't supported it in a very
> long time. Might be a good idea to keep it in this survey just to
> make sure its 0, then omit it from the next survey. :-)
I'd use "core-git, cogito (deprecated), StGIT, guilt, pg (deprecated),
other", then.
>> Changes in GIT (since year ago, or since you started using it)
> ...
>> 5. Which of the new features do you use?
>> (zero or more: multiple choice)
>> - git-gui, bundle, eol conversion, gitattributes,
>> submodules, worktree, release notes, user's manual,
>> reflog, stash, shallow clone, detached HEAD, fast-import,
>> mergetool, interactive rebase, commit template, blame
>> improvements, other (not mentioned here)
>
> Wow.
>
> This community has accomplished a lot since the last survey.
> That list covers most of the major items over the past year, if
> not all of them. But I'd never really seen it all written out
> in such a concise list; there's so much blood, sweat and tears
> in those topics from everyone on (and off) this mailing list.
> Reading it now is bringing back a lot of memories for me.
>
> Sorry, I just had a very emotional reaction to seeing how much we
> have managed to accomplish in so little time. Thank you to everyone
> who has made this list possible!
And that are only user visible features! This list does not include
improvements to git "engine", like better support for huge files, or
"thickening" downloaded pack during fetch, or non-feature improvements
to git UI, like git-gc, git-remote, changes to git-diff, git-log,
git-show, making separate remote layout default, etc.
On the other hand this list might include some features which were
present at the time of previous (first) survey, like reflog, but were
not enabled by default and had almost no porcelain support.
>> Getting help, staying in touch
>>
>> 1. Have you tried to get GIT help from other people?
>> - yes/no
>> 2. If yes, did you get these problems resolved quickly
>> and to your liking?
>> - yes/no
>
> Possible new item:
>
> Would commerical (paid) support from a support vendor be of
> interest to you/your organization?
This is a very good idea. I'd add this question to the list.
> I think Sam Vilain was suggesting he sell Git support
> to my day-job company, so my coworkers could call him and ask him
> questions, and he could ask me those same questions on #git, then
> mail me a 6-pack of beer[*1*] for my troubles. :)
>
>
> [*1*] And sadly I don't drink beer...
So what would be the proper compensation? Bottle of wine? Bar of
chocolate? ;-p
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2007-08-04 12:11 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-25 1:58 Git User's Survey 2007 Jakub Narebski
2007-07-25 16:19 ` Marco Costalba
2007-07-26 4:52 ` Steven Grimm
2007-07-27 11:20 ` [RFC] " Jakub Narebski
2007-07-27 12:21 ` Nguyen Thai Ngoc Duy
2007-07-27 13:01 ` Andy Parkins
2007-07-27 19:07 ` Jakub Narebski
2007-07-28 8:02 ` Andy Parkins
2007-07-29 16:50 ` Paolo Ciarrocchi
2007-07-29 17:05 ` Paolo Ciarrocchi
2007-07-30 0:21 ` Jakub Narebski
2007-07-30 3:35 ` Shawn O. Pearce
2007-07-30 13:40 ` Jakub Narebski
2007-07-30 7:44 ` Paolo Ciarrocchi
2007-07-30 13:26 ` Jakub Narebski
2007-07-30 19:26 ` David Kastrup
2007-07-30 21:12 ` Junio C Hamano
2007-07-30 21:37 ` Jakub Narebski
2007-07-30 22:38 ` David Kastrup
2007-07-30 21:25 ` Nguyen Thai Ngoc Duy
2007-07-30 21:35 ` Jakub Narebski
2007-07-30 20:56 ` [RFC (take 2) " Jakub Narebski
2007-07-31 0:32 ` Shawn O. Pearce
2007-07-31 0:45 ` Jakub Narebski
2007-07-31 1:09 ` Shawn O. Pearce
2007-07-31 1:24 ` Junio C Hamano
2007-07-31 1:31 ` Shawn O. Pearce
2007-07-31 11:22 ` Jakub Narebski
2007-07-31 11:33 ` Paolo Ciarrocchi
2007-07-31 12:30 ` Jakub Narebski
2007-07-31 16:35 ` Git User's Survey 2007 - web survey site Jakub Narebski
2007-07-31 19:07 ` Paolo Ciarrocchi
2007-08-02 4:51 ` Martin Langhoff
2007-08-02 13:04 ` Paolo Ciarrocchi
2007-08-04 0:50 ` [RFC (take 3)] Git User's Survey 2007 Jakub Narebski
2007-08-04 5:41 ` Shawn O. Pearce
2007-08-04 12:10 ` Jakub Narebski [this message]
2007-08-04 7:40 ` David Kastrup
2007-08-05 20:06 ` Jakub Narebski
2007-08-06 0:29 ` Johannes Schindelin
2007-08-05 9:30 ` Asger Ottar Alstrup
2007-08-06 1:17 ` Jakub Narebski
2007-08-06 5:48 ` Asger Ottar Alstrup
2007-08-06 15:44 ` Jakub Narebski
2007-08-05 20:51 ` [RFC (take 4)] " Jakub Narebski
2007-08-14 1:51 ` [RFC (final)] " Jakub Narebski
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=200708041410.22449.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.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).