git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: david@lang.hm
To: Elijah Newren <newren@gmail.com>
Cc: Jakub Narebski <jnareb@gmail.com>,
	git@vger.kernel.org, Stephan Beyer <s-beyer@gmx.net>
Subject: Re: Is incremental staging really the common mode? [Was: Re: Git User's Survey 2008 partial summary, part 4 - how do we use Git]
Date: Sun, 7 Sep 2008 17:32:09 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.1.10.0809071729310.8096@asgard.lang.hm> (raw)
In-Reply-To: <51419b2c0809071317g6f916b19p1c2792595be58047@mail.gmail.com>

On Sun, 7 Sep 2008, Elijah Newren wrote:

> Hi,
>
> On Sat, Sep 6, 2008 at 4:17 PM, Jakub Narebski <jnareb@gmail.com> wrote:
>> This is partial summary of Git User's Survey 2008 after more that 2000
>> (yes, that is more than _two thousands_ responses) just after the 6 days
>> of running the survey.  It is based on "Analysis" page for this survey:
>>  http://www.survs.com/shareResults?survey=M3PIVU72&rndm=OKJQ45LAG8
>>
> <snip>
>> git add + git commit   | 65% (1012)
>> git commit -a          | 63%  (981)
> <snip>
>> Analysis: strangely "git add + git commit" is slightly more used than
>> "git commit -a"; I would suspect that "git commit -a" would dominate a
>> bit over other forms of committing.  What is for me more suprising is
>> that "git commit <file>..." has such large presence in often used
>> commands; I would think that it should be mostly used as 'sometimes'
>> command.
>
> Does this data really compare usage of incremental staging of commits
> vs. non-incremental all-changes-included commits?
>
> You didn't have a git add + git commit -a, so if people feel like they
> have brand new files to add to the repository often, adding new files
> alone would cause them to mark the git add + git commit box as "often"
> (or maybe I was the only one dumb enough to think this was
> significantly related to adding new files?).  That alone could account
> for the difference, assuming others misunderstood as I did.

also, how many are doing 'git add .' or 'git add *' followed by git 
commit?

there were several commands listed that I have never heard of before and 
will want to research to see what they do to see if I should be using 
them.

next survey it would be handy to have links from each command you are 
asking about to a page that describes what it does and why you would use 
it (_not_ just a link to the man page for git add in the example above)

David Lang

  reply	other threads:[~2008-09-08  0:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-07 20:17 Is incremental staging really the common mode? [Was: Re: Git User's Survey 2008 partial summary, part 4 - how do we use Git] Elijah Newren
2008-09-08  0:32 ` david [this message]
2008-09-08  0:40   ` Is incremental staging really the common mode? Junio C Hamano
2008-09-08  0:45     ` david

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=alpine.DEB.1.10.0809071729310.8096@asgard.lang.hm \
    --to=david@lang.hm \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    --cc=newren@gmail.com \
    --cc=s-beyer@gmx.net \
    /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).