Junio C Hamano 13bb0ce6b7 builtin-add: fix exclude handling
After we finish walking the working tree to find paths to add, the
prune_directory() function checks the pathspecs to find typoes in
them.  When a given pathspec did not produce any match (either in the
untracked files, or paths already in the index), there are two cases:

 - "git add no-such-file", i.e. the pathspec was misspelled; or

 - "git add ignored-pattern.o", i.e. the pathspec exactly matches but is
   ignored by the traversal.

For the former, the function immediately errored out.  The latter were
queued in the dir structure and later used to give an error message with
"use -f if you really mean it" advice.

e96980e (builtin-add: simplify (and increase accuracy of) exclude
handling, 2007-06-12) somehow lost the latter.  This adds the logic back,
but with a bit of twist, as it uses collect_ignored option that does half
the necessary work during the traversal.

Signed-off-by: Junio C Hamano <gitster@pobox.com>
2010-02-28 23:47:04 -08:00
2009-12-09 15:38:51 -08:00
2009-09-14 02:23:36 -07:00
2008-07-19 11:17:43 -07:00
2009-06-30 16:12:24 -07:00
2009-04-17 21:05:49 -07:00
2009-06-18 09:22:46 -07:00
2009-12-22 12:32:39 -08:00
2009-10-30 20:18:31 -07:00
2009-12-26 14:03:16 -08:00
2010-01-07 15:35:55 -08:00
2008-08-28 20:50:10 -07:00
2009-12-26 14:03:16 -08:00
2009-08-05 12:39:33 -07:00
2009-11-23 21:54:39 -08:00
2009-12-26 14:03:16 -08:00
2009-12-05 11:39:13 -08:00
2009-11-23 21:54:39 -08:00
2009-08-07 22:35:17 -07:00
2009-11-23 22:30:08 -08:00
2009-02-13 17:27:58 -08:00
2009-11-20 23:53:55 -08:00
2009-11-20 23:51:23 -08:00
2009-12-26 14:03:16 -08:00
2009-11-23 22:24:01 -08:00
2009-09-13 01:32:26 -07:00
2008-10-10 08:39:20 -07:00
2009-05-01 16:07:29 -07:00
2009-11-22 16:28:14 -08:00
2009-10-03 06:04:38 -04:00
2009-05-20 00:02:24 -07:00
2009-06-18 09:22:46 -07:00
2009-12-30 01:25:21 -08:00
2008-11-02 16:36:40 -08:00
2010-02-28 23:47:04 -08:00
2010-02-28 23:47:04 -08:00
2009-11-23 22:24:01 -08:00
2009-12-08 22:47:09 -08:00
2009-12-13 23:40:24 -08:00
2009-12-08 22:47:09 -08:00
2008-07-13 14:12:48 -07:00
2009-12-26 14:11:46 -08:00
2009-11-23 22:24:01 -08:00
2008-09-07 23:52:16 -07:00
2009-11-04 17:58:15 -08:00
2009-11-13 12:16:30 -08:00
2009-11-22 16:28:14 -08:00
2009-04-22 19:02:12 -07:00
2010-01-07 15:35:52 -08:00
2008-10-25 12:09:31 -07:00
2009-08-21 18:47:53 -07:00
2009-08-21 18:47:53 -07:00
2009-11-30 14:44:22 -08:00
2009-12-26 14:20:09 -08:00
2009-11-23 21:25:55 -08:00
2009-12-26 14:03:16 -08:00
2009-12-26 14:03:16 -08:00
2009-02-14 21:27:35 -08:00
2009-11-23 22:30:08 -08:00
2009-11-04 17:58:15 -08:00
2008-07-21 19:11:50 -07:00
2009-11-04 17:58:15 -08:00
2008-03-02 15:11:07 -08:00
2009-01-17 18:30:41 -08:00
2009-08-30 22:04:46 -07:00
2009-12-26 14:03:16 -08:00
2009-12-26 14:03:16 -08:00
2009-04-20 13:44:14 -07:00
2009-12-10 16:20:59 -08:00
2009-11-22 16:14:48 -08:00
2009-11-13 12:20:47 -08:00
2009-07-22 21:57:41 -07:00
2009-12-27 23:01:32 -08:00

////////////////////////////////////////////////////////////////

	GIT - the stupid content tracker

////////////////////////////////////////////////////////////////

"git" can mean anything, depending on your mood.

 - random three-letter combination that is pronounceable, and not
   actually used by any common UNIX command.  The fact that it is a
   mispronunciation of "get" may or may not be relevant.
 - stupid. contemptible and despicable. simple. Take your pick from the
   dictionary of slang.
 - "global information tracker": you're in a good mood, and it actually
   works for you. Angels sing, and a light suddenly fills the room.
 - "goddamn idiotic truckload of sh*t": when it breaks

Git is a fast, scalable, distributed revision control system with an
unusually rich command set that provides both high-level operations
and full access to internals.

Git is an Open Source project covered by the GNU General Public License.
It was originally written by Linus Torvalds with help of a group of
hackers around the net. It is currently maintained by Junio C Hamano.

Please read the file INSTALL for installation instructions.

See Documentation/gittutorial.txt to get started, then see
Documentation/everyday.txt for a useful minimum set of commands, and
Documentation/git-commandname.txt for documentation of each command.
If git has been correctly installed, then the tutorial can also be
read with "man gittutorial" or "git help tutorial", and the
documentation of each command with "man git-commandname" or "git help
commandname".

CVS users may also want to read Documentation/gitcvs-migration.txt
("man gitcvs-migration" or "git help cvs-migration" if git is
installed).

Many Git online resources are accessible from http://git-scm.com/
including full documentation and Git related tools.

The user discussion and development of Git take place on the Git
mailing list -- everyone is welcome to post bug reports, feature
requests, comments and patches to git@vger.kernel.org. To subscribe
to the list, send an email with just "subscribe git" in the body to
majordomo@vger.kernel.org. The mailing list archives are available at
http://marc.theaimsgroup.com/?l=git and other archival sites.

The messages titled "A note from the maintainer", "What's in
git.git (stable)" and "What's cooking in git.git (topics)" and
the discussion following them on the mailing list give a good
reference for project status, development direction and
remaining tasks.
Description
No description provided
Readme 741 MiB
Languages
C 50.4%
Shell 38.7%
Perl 4.4%
Tcl 3.1%
Python 0.8%
Other 2.4%