Skip to content

Commit

Permalink
Merge branch 'cn/eradicate-working-copy' into maint
Browse files Browse the repository at this point in the history
* cn/eradicate-working-copy:
  Remove 'working copy' from the documentation and C code
  • Loading branch information
gitster committed Oct 26, 2011
2 parents f0911b9 + f7d650c commit a5ad8d1
Show file tree
Hide file tree
Showing 4 changed files with 6 additions and 6 deletions.
6 changes: 3 additions & 3 deletions Documentation/config.txt
Expand Up @@ -147,7 +147,7 @@ advice.*::

core.fileMode::
If false, the executable bit differences between the index and
the working copy are ignored; useful on broken filesystems like FAT.
the working tree are ignored; useful on broken filesystems like FAT.
See linkgit:git-update-index[1].
+
The default is true, except linkgit:git-clone[1] or linkgit:git-init[1]
Expand Down Expand Up @@ -179,7 +179,7 @@ is created.

core.trustctime::
If false, the ctime differences between the index and the
working copy are ignored; useful when the inode change time
working tree are ignored; useful when the inode change time
is regularly modified by something outside Git (file system
crawlers and some backup systems).
See linkgit:git-update-index[1]. True by default.
Expand Down Expand Up @@ -292,7 +292,7 @@ core.ignoreStat::
If true, commands which modify both the working tree and the index
will mark the updated paths with the "assume unchanged" bit in the
index. These marked files are then assumed to stay unchanged in the
working copy, until you mark them otherwise manually - Git will not
working tree, until you mark them otherwise manually - Git will not
detect the file changes by lstat() calls. This is useful on systems
where those are very slow, such as Microsoft Windows.
See linkgit:git-update-index[1].
Expand Down
2 changes: 1 addition & 1 deletion Documentation/git-svn.txt
Expand Up @@ -318,7 +318,7 @@ Any other arguments are passed directly to 'git log'
Show what revision and author last modified each line of a file. The
output of this mode is format-compatible with the output of
`svn blame' by default. Like the SVN blame command,
local uncommitted changes in the working copy are ignored;
local uncommitted changes in the working tree are ignored;
the version of the file in the HEAD revision is annotated. Unknown
arguments are passed directly to 'git blame'.
+
Expand Down
2 changes: 1 addition & 1 deletion diff-lib.c
Expand Up @@ -289,7 +289,7 @@ static void show_new_file(struct rev_info *revs,

/*
* New file in the index: it might actually be different in
* the working copy.
* the working tree.
*/
if (get_stat_data(new, &sha1, &mode, cached, match_missing,
&dirty_submodule, &revs->diffopt) < 0)
Expand Down
2 changes: 1 addition & 1 deletion merge-recursive.c
Expand Up @@ -390,7 +390,7 @@ static void record_df_conflict_files(struct merge_options *o,
struct string_list *entries)
{
/* If there is a D/F conflict and the file for such a conflict
* currently exist in the working copy, we want to allow it to be
* currently exist in the working tree, we want to allow it to be
* removed to make room for the corresponding directory if needed.
* The files underneath the directories of such D/F conflicts will
* be processed before the corresponding file involved in the D/F
Expand Down

0 comments on commit a5ad8d1

Please sign in to comment.