All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Lars Vogel <lars.vogel@vogella.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Documentation: read-tree consistent usage of working tree
Date: Tue, 25 Aug 2015 09:31:12 -0700	[thread overview]
Message-ID: <xmqqpp2b1ga7.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <1439841979-27110-1-git-send-email-Lars.Vogel@vogella.com> (Lars Vogel's message of "Mon, 17 Aug 2015 22:06:19 +0200")

Lars Vogel <lars.vogel@vogella.com> writes:

> http://git-scm.com/docs/git-clone speaks only about working tree, the
> usage of "working directory" for working tree is confusing. Working
> directory describes the current directory while working tree describes
> all files and sub directories.

Actually I think the $cwd is the "Current working directory"; the
phrase "Working directory" alone does not specifically refer to $cwd.

Being consistent to call the checked out file hierarchy "working tree"
is probably a good idea nevertheless.

> Signed-off-by: Lars Vogel <Lars.Vogel@vogella.com>
> ---

If you apply this patch and then run

    $ git grep -B1 '^directory' Documentation/git-read-tree.txt

you would notice that the patch has missed a few more.

Also

    $ git grep 'work tree' Documentation/git-read-tree.txt

has a handful of hits.

Perhaps try again?

Thanks.

  reply	other threads:[~2015-08-25 16:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-17 20:06 [PATCH] Documentation: read-tree consistent usage of working tree Lars Vogel
2015-08-25 16:31 ` Junio C Hamano [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-08-17 20:03 Lars Vogel

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=xmqqpp2b1ga7.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=lars.vogel@vogella.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.