git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Haggerty <mhagger@alum.mit.edu>
To: "Carlos Martín Nieto" <cmn@elego.de>
Cc: git@vger.kernel.org
Subject: Re: Worktree vs. working copy
Date: Tue, 20 Sep 2011 12:39:54 +0200	[thread overview]
Message-ID: <4E786D7A.8020503@alum.mit.edu> (raw)
In-Reply-To: <1316505022.13996.12.camel@bee.lab.cmartin.tk>

On 09/20/2011 09:50 AM, Carlos Martín Nieto wrote:
> I've noticed that in some places in git.git, the term 'working copy' is
> used. Mostly it's in git-cvsserver which I guess it's fine, but the
> git-config man page talks about the 'working copy' in three places.
> 
>     $ git grep 'worktree' | wc -l
>     412
>     $ git grep 'working copy' | grep -v ^git-cvsserver |  wc -l
>     32

Please note that the string "worktree" mostly appears in code
(presumably as variable names) and in the names of options.  In text,
"working tree" is far more common than either:

$ git grep -i 'worktree' -- '*.txt' | wc -l
50
$ git grep -i 'working copy' -- '*.txt' | wc -l
6
$ git grep -i 'working tree' -- '*.txt' | wc -l
330

Michael

-- 
Michael Haggerty
mhagger@alum.mit.edu
http://softwareswirl.blogspot.com/

  reply	other threads:[~2011-09-20 10:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-20  7:50 Worktree vs. working copy Carlos Martín Nieto
2011-09-20 10:39 ` Michael Haggerty [this message]
2011-09-20 10:48   ` Nguyen Thai Ngoc Duy
2011-09-20 10:56 ` Ramkumar Ramachandra
2011-09-20 19:10   ` Junio C Hamano
2011-09-20 20:25     ` Carlos Martín Nieto
2011-09-20 21:45       ` Junio C Hamano

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=4E786D7A.8020503@alum.mit.edu \
    --to=mhagger@alum.mit.edu \
    --cc=cmn@elego.de \
    --cc=git@vger.kernel.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).