| commit | 464a8a7a15fc70efbcf56c4569f0f7275a9c76fe | |
| author | J. Bruce Fields <bfields@puzzle.fieldses.org> | |
| Fri, 25 May 2007 00:28:14 +0000 (24 20:28 -0400) | ||
| committer | J. Bruce Fields <bfields@citi.umich.edu> | |
| Sun, 26 Aug 2007 14:35:16 +0000 (26 10:35 -0400) | ||
| tree | 0289a8abd616bf2cabe858ef8ea2765672576dee | treesnapshot (tar.gz zip) |
| parent | b13ef4916ac5a25cc5897f85ba0b4c5953cff609 | commitdiff |
user-manual: edit "ignoring files" for conciseness
The immediate motivation for writing this section was to explain the
various places ignore patterns could be used. However, I still think
.gitignore is the case most people will want to learn about first. It
also makes it a bit more concrete to introduce ignore patterns in the
context of .gitignore first. And the existance of gitignore(5) relieves
the pressure to explain it all here.
So, stick to the .gitignore example, with only a brief mention of the
others, explain the syntax only by example, and leave the rest to
gitignore(5).
Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu>
Cc: Johan Herland <johan@herland.net>
The immediate motivation for writing this section was to explain the
various places ignore patterns could be used. However, I still think
.gitignore is the case most people will want to learn about first. It
also makes it a bit more concrete to introduce ignore patterns in the
context of .gitignore first. And the existance of gitignore(5) relieves
the pressure to explain it all here.
So, stick to the .gitignore example, with only a brief mention of the
others, explain the syntax only by example, and leave the rest to
gitignore(5).
Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu>
Cc: Johan Herland <johan@herland.net>
| Documentation/user-manual.txt | diffblobblamehistory |