Permalink
Browse files

War on whitespace

This uses "git-apply --whitespace=strip" to fix whitespace errors that have
crept in to our source files over time.  There are a few files that need
to have trailing whitespaces (most notably, test vectors).  The results
still passes the test, and build result in Documentation/ area is unchanged.

Signed-off-by: Junio C Hamano <gitster@pobox.com>
  • Loading branch information...
1 parent d44c782 commit a6080a0a44d5ead84db3dabbbc80e82df838533d @gitster gitster committed Jun 7, 2007
Showing with 645 additions and 852 deletions.
  1. +0 −2 Documentation/RelNotes-1.5.0.4.txt
  2. +0 −2 Documentation/RelNotes-1.5.0.5.txt
  3. +0 −1 Documentation/RelNotes-1.5.0.6.txt
  4. +0 −1 Documentation/RelNotes-1.5.1.3.txt
  5. +7 −7 Documentation/SubmittingPatches
  6. +0 −2 Documentation/asciidoc.conf
  7. +0 −2 Documentation/config.txt
  8. +23 −23 Documentation/core-tutorial.txt
  9. +10 −11 Documentation/diff-format.txt
  10. +2 −2 Documentation/diff-options.txt
  11. +1 −2 Documentation/diffcore.txt
  12. +286 −286 Documentation/docbook-xsl.css
  13. +0 −1 Documentation/fetch-options.txt
  14. +0 −1 Documentation/git-add.txt
  15. +0 −1 Documentation/git-am.txt
  16. +0 −1 Documentation/git-apply.txt
  17. +22 −23 Documentation/git-archimport.txt
  18. +1 −2 Documentation/git-bisect.txt
  19. +0 −1 Documentation/git-branch.txt
  20. +0 −1 Documentation/git-cat-file.txt
  21. +0 −1 Documentation/git-check-attr.txt
  22. +0 −1 Documentation/git-checkout-index.txt
  23. +0 −1 Documentation/git-checkout.txt
  24. +0 −1 Documentation/git-cherry-pick.txt
  25. +0 −1 Documentation/git-cherry.txt
  26. +0 −1 Documentation/git-clone.txt
  27. +1 −2 Documentation/git-commit-tree.txt
  28. +0 −1 Documentation/git-config.txt
  29. +0 −1 Documentation/git-convert-objects.txt
  30. +0 −1 Documentation/git-count-objects.txt
  31. +7 −8 Documentation/git-cvsexportcommit.txt
  32. +6 −7 Documentation/git-cvsimport.txt
  33. +0 −1 Documentation/git-daemon.txt
  34. +0 −1 Documentation/git-describe.txt
  35. +1 −2 Documentation/git-diff-files.txt
  36. +1 −2 Documentation/git-diff-index.txt
  37. +0 −1 Documentation/git-diff-tree.txt
  38. +0 −1 Documentation/git-diff.txt
  39. +0 −1 Documentation/git-fast-import.txt
  40. +0 −1 Documentation/git-fmt-merge-msg.txt
  41. +0 −1 Documentation/git-format-patch.txt
  42. +0 −1 Documentation/git-fsck.txt
  43. +0 −1 Documentation/git-get-tar-commit-id.txt
  44. +0 −1 Documentation/git-grep.txt
  45. +1 −2 Documentation/git-hash-object.txt
  46. +0 −1 Documentation/git-http-fetch.txt
  47. +1 −1 Documentation/git-http-push.txt
  48. +0 −1 Documentation/git-index-pack.txt
  49. +0 −1 Documentation/git-init-db.txt
  50. +0 −1 Documentation/git-init.txt
  51. +0 −1 Documentation/git-instaweb.txt
  52. +0 −1 Documentation/git-local-fetch.txt
  53. +0 −1 Documentation/git-log.txt
  54. +0 −1 Documentation/git-ls-files.txt
  55. +0 −1 Documentation/git-ls-remote.txt
  56. +0 −1 Documentation/git-ls-tree.txt
  57. +0 −1 Documentation/git-mailinfo.txt
  58. +0 −1 Documentation/git-mailsplit.txt
  59. +0 −1 Documentation/git-merge-base.txt
  60. +1 −2 Documentation/git-merge-index.txt
  61. +0 −1 Documentation/git-merge-one-file.txt
  62. +0 −1 Documentation/git-merge-tree.txt
  63. +1 −1 Documentation/git-merge.txt
  64. +0 −1 Documentation/git-mergetool.txt
  65. +0 −1 Documentation/git-mktag.txt
  66. +0 −1 Documentation/git-mktree.txt
  67. +0 −1 Documentation/git-mv.txt
  68. +0 −1 Documentation/git-name-rev.txt
  69. +0 −1 Documentation/git-p4import.txt
  70. +0 −1 Documentation/git-pack-objects.txt
  71. +1 −2 Documentation/git-pack-redundant.txt
  72. +0 −1 Documentation/git-patch-id.txt
  73. +0 −1 Documentation/git-peek-remote.txt
  74. +0 −1 Documentation/git-prune-packed.txt
  75. +0 −1 Documentation/git-prune.txt
  76. +0 −1 Documentation/git-pull.txt
  77. +0 −1 Documentation/git-push.txt
  78. +0 −1 Documentation/git-quiltimport.txt
  79. +0 −1 Documentation/git-read-tree.txt
  80. +0 −1 Documentation/git-rebase.txt
  81. +0 −1 Documentation/git-reflog.txt
  82. +0 −1 Documentation/git-relink.txt
  83. +0 −1 Documentation/git-remote.txt
  84. +0 −1 Documentation/git-repack.txt
  85. +0 −1 Documentation/git-request-pull.txt
  86. +0 −1 Documentation/git-rev-parse.txt
  87. +0 −1 Documentation/git-revert.txt
  88. +0 −1 Documentation/git-rm.txt
  89. +0 −1 Documentation/git-runstatus.txt
  90. +1 −2 Documentation/git-send-email.txt
  91. +0 −1 Documentation/git-sh-setup.txt
  92. +0 −1 Documentation/git-shell.txt
  93. +0 −1 Documentation/git-shortlog.txt
  94. +0 −1 Documentation/git-show-index.txt
  95. +0 −1 Documentation/git-show.txt
  96. +0 −1 Documentation/git-ssh-fetch.txt
  97. +0 −1 Documentation/git-ssh-upload.txt
  98. +0 −1 Documentation/git-status.txt
  99. +0 −1 Documentation/git-stripspace.txt
  100. +0 −1 Documentation/git-svnimport.txt
  101. +0 −1 Documentation/git-tar-tree.txt
  102. +0 −1 Documentation/git-unpack-file.txt
  103. +0 −1 Documentation/git-unpack-objects.txt
  104. +4 −5 Documentation/git-update-index.txt
  105. +0 −1 Documentation/git-update-server-info.txt
  106. +0 −1 Documentation/git-var.txt
  107. +0 −1 Documentation/git-verify-pack.txt
  108. +0 −1 Documentation/git-verify-tag.txt
  109. +0 −1 Documentation/git-whatchanged.txt
  110. +0 −1 Documentation/git-write-tree.txt
  111. +0 −1 Documentation/git.txt
  112. +0 −1 Documentation/gitk.txt
  113. +9 −11 Documentation/howto/rebase-and-edit.txt
  114. +5 −7 Documentation/howto/rebase-from-internal-branch.txt
  115. +0 −1 Documentation/howto/rebuild-from-update-hook.txt
  116. +1 −1 Documentation/howto/revert-branch-rebase.txt
  117. +6 −7 Documentation/howto/separating-topic-branches.txt
  118. +0 −1 Documentation/howto/use-git-daemon.txt
  119. +0 −1 Documentation/merge-options.txt
  120. +0 −1 Documentation/pretty-formats.txt
  121. +0 −1 Documentation/pretty-options.txt
  122. +1 −1 Documentation/pull-fetch-param.txt
  123. +0 −1 Documentation/repository-layout.txt
  124. +4 −4 Documentation/technical/pack-format.txt
  125. +19 −19 Documentation/user-manual.txt
  126. +0 −2 GIT-VERSION-GEN
  127. +1 −2 INSTALL
  128. +2 −2 arm/sha1.c
  129. +0 −1 arm/sha1_arm.S
  130. +0 −1 builtin-annotate.c
  131. +1 −1 builtin-diff-index.c
  132. +0 −1 builtin-fmt-merge-msg.c
  133. +2 −2 builtin-fsck.c
  134. +1 −1 builtin-ls-files.c
  135. +0 −1 builtin-name-rev.c
  136. +1 −1 builtin-pack-objects.c
  137. +0 −1 builtin-rerere.c
  138. +0 −1 builtin-shortlog.c
  139. +1 −1 cache.h
  140. +7 −7 commit.c
  141. +1 −1 commit.h
  142. +0 −1 compat/mmap.c
  143. +1 −2 config.c
  144. +0 −1 config.mak.in
  145. +1 −1 connect.c
  146. +0 −1 contrib/README
  147. +0 −1 contrib/blameview/README
  148. +0 −2 contrib/gitview/gitview
  149. +1 −1 contrib/hooks/post-receive-email
  150. +0 −2 contrib/remotes2config.sh
  151. +1 −1 convert-objects.c
  152. +0 −1 copy.c
  153. +0 −1 ctype.c
  154. +2 −2 daemon.c
  155. +5 −5 date.c
  156. +1 −1 diff-lib.c
  157. +2 −2 diff.c
  158. +1 −1 diffcore-pickaxe.c
  159. +1 −1 entry.c
  160. +0 −2 environment.c
  161. +1 −1 fetch-pack.c
  162. +2 −2 fetch.c
  163. +87 −88 git-archimport.perl
  164. +2 −2 git-checkout.sh
  165. +2 −3 git-clone.sh
  166. +1 −1 git-commit.sh
  167. +1 −1 git-cvsexportcommit.perl
  168. +6 −6 git-cvsimport.perl
  169. +0 −2 git-gui/GIT-VERSION-GEN
  170. +0 −1 git-gui/lib/class.tcl
  171. +1 −1 git-merge-one-file.sh
  172. +0 −1 git-p4import.py
  173. +2 −2 git-svnimport.perl
  174. +2 −3 git-tag.sh
  175. +0 −1 git-verify-tag.sh
  176. +1 −1 git.spec.in
  177. +1 −1 gitk
  178. +0 −1 gitweb/README
  179. +0 −2 help.c
  180. +1 −1 http-fetch.c
  181. +1 −1 http-push.c
  182. +1 −1 http.c
  183. +1 −1 imap-send.c
  184. +4 −4 local-fetch.c
  185. +0 −1 lockfile.c
  186. +0 −1 mailmap.c
  187. +0 −1 match-trees.c
  188. +1 −1 merge-index.c
  189. +1 −1 mktag.c
  190. +9 −10 mozilla-sha1/sha1.c
  191. +9 −9 mozilla-sha1/sha1.h
  192. +0 −2 object-refs.c
  193. +1 −1 object.h
  194. +2 −2 pack-redundant.c
  195. +1 −1 patch-id.c
  196. +0 −1 path-list.c
  197. +0 −1 perl/Makefile
  198. +1 −1 pkt-line.c
  199. +1 −1 ppc/sha1.c
  200. +5 −5 read-cache.c
  201. +1 −1 rsh.h
  202. +2 −2 setup.c
  203. +4 −4 sha1_file.c
  204. +0 −1 shallow.c
  205. +5 −5 ssh-upload.c
  206. +0 −1 strbuf.c
  207. +0 −1 t/Makefile
  208. +1 −1 t/lib-read-tree-m-3way.sh
  209. +1 −1 t/t0000-basic.sh
  210. +0 −1 t/t1200-tutorial.sh
  211. +0 −1 t/t1300-repo-config.sh
  212. +0 −2 t/t2000-checkout-cache-clash.sh
  213. +0 −1 t/t2001-checkout-cache-clash.sh
  214. +0 −1 t/t3030-merge-recursive.sh
  215. +0 −1 t/t3403-rebase-skip.sh
  216. +0 −1 t/t4006-diff-mode.sh
  217. +0 −1 t/t4100-apply-stat.sh
  218. +0 −1 t/t4110-apply-scan.sh
  219. +8 −8 t/t4112-apply-renames.sh
  220. +0 −1 t/t4118-apply-empty-context.sh
  221. +1 −1 t/t4119-apply-config.sh
  222. +0 −1 t/t4121-apply-diffs.sh
  223. +0 −1 t/t4122-apply-symlink-inside.sh
  224. +0 −2 t/t4200-rerere.sh
  225. +1 −1 t/t5400-send-pack.sh
  226. +0 −1 t/t5520-pull.sh
  227. +0 −1 t/t5710-info-alternate.sh
  228. +8 −8 t/t6000lib.sh
  229. +4 −4 t/t6002-rev-list-bisect.sh
  230. +1 −1 t/t6021-merge-criss-cross.sh
  231. +0 −1 t/t6023-merge-file.sh
  232. +0 −1 t/t6030-bisect-porcelain.sh
  233. +0 −1 t/t6101-rev-parse-parents.sh
  234. +0 −1 t/t9107-git-svn-migrate.sh
  235. +0 −2 t/t9111/svnsync.dump
  236. +1 −1 t/test-lib.sh
  237. +0 −1 templates/hooks--commit-msg
  238. +0 −1 templates/hooks--post-receive
  239. +0 −1 templates/hooks--pre-applypatch
  240. +0 −1 templates/hooks--pre-commit
  241. +0 −1 tree-walk.c
  242. +1 −1 upload-pack.c
  243. +2 −2 var.c
  244. +0 −2 xdiff-interface.c
  245. +0 −1 xdiff/xdiff.h
  246. +0 −1 xdiff/xdiffi.c
  247. +0 −1 xdiff/xdiffi.h
  248. +0 −1 xdiff/xemit.c
  249. +0 −1 xdiff/xemit.h
  250. +0 −1 xdiff/xinclude.h
  251. +0 −1 xdiff/xmacros.h
  252. +0 −1 xdiff/xprepare.c
  253. +0 −1 xdiff/xprepare.h
  254. +0 −1 xdiff/xtypes.h
  255. +0 −1 xdiff/xutils.c
  256. +0 −1 xdiff/xutils.h
@@ -20,5 +20,3 @@ Fixes since v1.5.0.3
* Documentation updates
* User manual updates
-
-
@@ -24,5 +24,3 @@ Fixes since v1.5.0.3
* Documentation updates
* User manual updates
-
-
@@ -19,4 +19,3 @@ Fixes since v1.5.0.5
- user-manual has better cross references.
- gitweb installation/deployment procedure is now documented.
-
@@ -43,4 +43,3 @@ Fixes since v1.5.1.2
description was given by the caller.
Also contains various documentation updates.
-
@@ -296,15 +296,15 @@ diff --git a/pico/pico.c b/pico/pico.c
--- a/pico/pico.c
+++ b/pico/pico.c
@@ -219,7 +219,9 @@ PICO *pm;
- switch(pico_all_done){ /* prepare for/handle final events */
- case COMP_EXIT : /* already confirmed */
- packheader();
+ switch(pico_all_done){ /* prepare for/handle final events */
+ case COMP_EXIT : /* already confirmed */
+ packheader();
+#if 0
- stripwhitespace();
+ stripwhitespace();
+#endif
- c |= COMP_EXIT;
- break;
-
+ c |= COMP_EXIT;
+ break;
+
(Daniel Barkalow)
@@ -54,5 +54,3 @@ ifdef::backend-xhtml11[]
[gitlink-inlinemacro]
<a href="{target}.html">{target}{0?({0})}</a>
endif::backend-xhtml11[]
-
-
View
@@ -682,5 +682,3 @@ receive.denyNonFastForwards::
transfer.unpackLimit::
When `fetch.unpackLimit` or `receive.unpackLimit` are
not set, the value of this variable is used instead.
-
-
@@ -9,11 +9,11 @@ repository, mainly because being hands-on and using explicit examples is
often the best way of explaining what is going on.
In normal life, most people wouldn't use the "core" git programs
-directly, but rather script around them to make them more palatable.
+directly, but rather script around them to make them more palatable.
Understanding the core git stuff may help some people get those scripts
done, though, and it may also be instructive in helping people
understand what it is that the higher-level helper scripts are actually
-doing.
+doing.
The core git is often called "plumbing", with the prettier user
interfaces on top of it called "porcelain". You may not want to use the
@@ -41,7 +41,7 @@ Creating a new git repository couldn't be easier: all git repositories start
out empty, and the only thing you need to do is find yourself a
subdirectory that you want to use as a working tree - either an empty
one for a totally new project, or an existing working tree that you want
-to import into git.
+to import into git.
For our first example, we're going to start a totally new repository from
scratch, with no pre-existing files, and we'll call it `git-tutorial`.
@@ -169,7 +169,7 @@ $ ls .git/objects/??/*
and see two files:
----------------
-.git/objects/55/7db03de997c86a4a028e1ebd3a1ceb225be238
+.git/objects/55/7db03de997c86a4a028e1ebd3a1ceb225be238
.git/objects/f2/4c74a2e500f5ee1332c86b94199f52b1d1d962
----------------
@@ -220,7 +220,7 @@ you have not actually really "checked in" your files into git so far,
you've only *told* git about them.
However, since git knows about them, you can now start using some of the
-most basic git commands to manipulate the files or look at their status.
+most basic git commands to manipulate the files or look at their status.
In particular, let's not even check in the two files into git yet, we'll
start off by adding another line to `hello` first:
@@ -350,7 +350,7 @@ Making a change
Remember how we did the `git-update-index` on file `hello` and then we
changed `hello` afterward, and could compare the new state of `hello` with the
-state we saved in the index file?
+state we saved in the index file?
Further, remember how I said that `git-write-tree` writes the contents
of the *index* file to the tree, and thus what we just committed was in
@@ -370,7 +370,7 @@ file and the working tree, `git-diff-index` shows the differences
between a committed *tree* and either the index file or the working
tree. In other words, `git-diff-index` wants a tree to be diffed
against, and before we did the commit, we couldn't do that, because we
-didn't have anything to diff against.
+didn't have anything to diff against.
But now we can do
@@ -379,7 +379,7 @@ $ git-diff-index -p HEAD
----------------
(where `-p` has the same meaning as it did in `git-diff-files`), and it
-will show us the same difference, but for a totally different reason.
+will show us the same difference, but for a totally different reason.
Now we're comparing the working tree not against the index file,
but against the tree we just wrote. It just so happens that those two
are obviously the same, so we get the same result.
@@ -398,7 +398,7 @@ working tree, but when given the `\--cached` flag, it is told to
instead compare against just the index cache contents, and ignore the
current working tree state entirely. Since we just wrote the index
file to HEAD, doing `git-diff-index \--cached -p HEAD` should thus return
-an empty set of differences, and that's exactly what it does.
+an empty set of differences, and that's exactly what it does.
[NOTE]
================
@@ -549,7 +549,7 @@ $ git-whatchanged -p --root
----------------
and you will see exactly what has changed in the repository over its
-short history.
+short history.
[NOTE]
The `\--root` flag is a flag to `git-diff-tree` to tell it to
@@ -637,7 +637,7 @@ So the mental model of "the git information is always tied directly to
the working tree that it describes" may not be technically 100%
accurate, but it's a good model for all normal use.
-This has two implications:
+This has two implications:
- if you grow bored with the tutorial repository you created (or you've
made a mistake and want to start all over), you can just do simple
@@ -705,7 +705,7 @@ Many (most?) public remote repositories will not contain any of
the checked out files or even an index file, and will *only* contain the
actual core git files. Such a repository usually doesn't even have the
`.git` subdirectory, but has all the git files directly in the
-repository.
+repository.
To create your own local live copy of such a "raw" git repository, you'd
first create your own subdirectory for the project, and then copy the
@@ -718,7 +718,7 @@ $ cd my-git
$ rsync -rL rsync://rsync.kernel.org/pub/scm/git/git.git/ .git
----------------
-followed by
+followed by
----------------
$ git-read-tree HEAD
@@ -738,7 +738,7 @@ up-to-date (so that you don't have to refresh it afterward), and the
`-a` flag means "check out all files" (if you have a stale copy or an
older version of a checked out tree you may also need to add the `-f`
flag first, to tell git-checkout-index to *force* overwriting of any old
-files).
+files).
Again, this can all be simplified with
@@ -751,7 +751,7 @@ $ git checkout
which will end up doing all of the above for you.
You have now successfully copied somebody else's (mine) remote
-repository, and checked it out.
+repository, and checked it out.
Creating a new branch
@@ -760,14 +760,14 @@ Creating a new branch
Branches in git are really nothing more than pointers into the git
object database from within the `.git/refs/` subdirectory, and as we
already discussed, the `HEAD` branch is nothing but a symlink to one of
-these object pointers.
+these object pointers.
You can at any time create a new branch by just picking an arbitrary
point in the project history, and just writing the SHA1 name of that
object into a file under `.git/refs/heads/`. You can use any filename you
want (and indeed, subdirectories), but the convention is that the
"normal" branch is called `master`. That's just a convention, though,
-and nothing enforces it.
+and nothing enforces it.
To show that as an example, let's go back to the git-tutorial repository we
used earlier, and create a branch in it. You do that by simply just
@@ -778,7 +778,7 @@ $ git checkout -b mybranch
------------
will create a new branch based at the current `HEAD` position, and switch
-to it.
+to it.
[NOTE]
================================================
@@ -825,7 +825,7 @@ checking it out and switching to it. If so, just use the command
$ git branch <branchname> [startingpoint]
------------
-which will simply _create_ the branch, but will not do anything further.
+which will simply _create_ the branch, but will not do anything further.
You can then later -- once you decide that you want to actually develop
on that branch -- switch to that branch with a regular `git checkout`
with the branchname as the argument.
@@ -884,7 +884,7 @@ $ gitk --all
will show you graphically both of your branches (that's what the `\--all`
means: normally it will just show you your current `HEAD`) and their
histories. You can also see exactly how they came to be from a common
-source.
+source.
Anyway, let's exit `gitk` (`^Q` or the File menu), and decide that we want
to merge the work we did on the `mybranch` branch into the `master`
@@ -905,8 +905,8 @@ of it as it can automatically (which in this case is just merge the `example`
file, which had no differences in the `mybranch` branch), and say:
----------------
- Auto-merging hello
- CONFLICT (content): Merge conflict in hello
+ Auto-merging hello
+ CONFLICT (content): Merge conflict in hello
Automatic merge failed; fix up by hand
----------------
@@ -1387,7 +1387,7 @@ repository. Kernel.org mirror network takes care of the
propagation to other publicly visible machines:
------------
-$ git push master.kernel.org:/pub/scm/git/git.git/
+$ git push master.kernel.org:/pub/scm/git/git.git/
------------
@@ -1,7 +1,7 @@
The output format from "git-diff-index", "git-diff-tree" and
"git-diff-files" are very similar.
-These commands all compare two sets of things; what is
+These commands all compare two sets of things; what is
compared differs:
git-diff-index <tree-ish>::
@@ -139,28 +139,28 @@ index fabadb8,cc95eb0..4866510
--- a/describe.c
+++ b/describe.c
@@@ -98,20 -98,12 +98,20 @@@
- return (a_date > b_date) ? -1 : (a_date == b_date) ? 0 : 1;
+ return (a_date > b_date) ? -1 : (a_date == b_date) ? 0 : 1;
}
-
+
- static void describe(char *arg)
-static void describe(struct commit *cmit, int last_one)
++static void describe(char *arg, int last_one)
{
+ unsigned char sha1[20];
+ struct commit *cmit;
- struct commit_list *list;
- static int initialized = 0;
- struct commit_name *n;
-
+ struct commit_list *list;
+ static int initialized = 0;
+ struct commit_name *n;
+
+ if (get_sha1(arg, sha1) < 0)
+ usage(describe_usage);
+ cmit = lookup_commit_reference(sha1);
+ if (!cmit)
+ usage(describe_usage);
+
- if (!initialized) {
- initialized = 1;
- for_each_ref(get_name);
+ if (!initialized) {
+ initialized = 1;
+ for_each_ref(get_name);
------------
1. It is preceded with a "git diff" header, that looks like
@@ -233,4 +233,3 @@ parents). When shown by `git diff-files -c`, it compares the
two unresolved merge parents with the working tree file
(i.e. file1 is stage 2 aka "our version", file2 is stage 3 aka
"their version").
-
@@ -100,8 +100,8 @@
that matches other criteria, nothing is selected.
--find-copies-harder::
- For performance reasons, by default, -C option finds copies only
- if the original file of the copy was modified in the same
+ For performance reasons, by default, -C option finds copies only
+ if the original file of the copy was modified in the same
changeset. This flag makes the command
inspect unmodified files as candidates for the source of
copy. This is a very expensive operation for large
@@ -71,7 +71,7 @@ The first transformation in the chain is diffcore-pathspec, and
is controlled by giving the pathname parameters to the
git-diff-* commands on the command line. The pathspec is used
to limit the world diff operates in. It removes the filepairs
-outside the specified set of pathnames. E.g. If the input set
+outside the specified set of pathnames. E.g. If the input set
of filepairs included:
------------------------------------------------
@@ -269,4 +269,3 @@ Documentation
*.c
t
------------------------------------------------
-
Oops, something went wrong.

0 comments on commit a6080a0

Please sign in to comment.