Junio C Hamano 77b15bbd88 apply --whitespace=warn/error: diagnose blank at EOF
"git apply" strips new blank lines at EOF under --whitespace=fix option,
but neigher --whitespace=warn nor --whitespace=error paid any attention to
these errors.

Introduce a new whitespace error class, blank-at-eof, to make the
whitespace error handling more consistent.

The patch adds a new "linenr" field to the struct fragment in order to
record which line the hunk started in the input file, but this is needed
solely for reporting purposes.  The detection of this class of whitespace
errors cannot be done while parsing a patch like we do for all the other
classes of whitespace errors.  It instead has to wait until we find where
to apply the hunk, but at that point, we do not have an access to the
original line number in the input file anymore, hence the new field.

Depending on your point of view, this may be a bugfix that makes warn and
error in line with fix.  Or you could call it a new feature.  The line
between them is somewhat fuzzy in this case.

Strictly speaking, triggering more errors than before is a change in
behaviour that is not backward compatible, even though the reason for the
change is because the code was not checking for an error that it should
have.  People who do not want added blank lines at EOF to trigger an error
can disable the new error class.

Signed-off-by: Junio C Hamano <gitster@pobox.com>
2009-09-04 11:50:26 -07:00
2007-06-07 00:04:01 -07:00
2008-12-19 19:27:35 -08:00
2007-06-07 00:04:01 -07:00
2007-06-07 00:04:01 -07:00
2008-07-07 02:17:23 -07:00
2008-07-19 11:25:51 -07:00
2008-06-30 22:45:50 -07:00
2008-07-19 11:17:43 -07:00
2008-07-19 11:17:43 -07:00
2008-10-26 16:19:59 -07:00
2007-05-30 15:03:50 -07:00
2008-07-20 17:53:17 -07:00
2007-06-07 00:04:01 -07:00
2008-07-13 14:12:48 -07:00
2008-09-19 22:05:31 -07:00
2008-07-16 17:22:50 -07:00
2008-08-28 20:50:10 -07:00
2008-03-14 00:16:42 -07:00
2008-08-03 14:14:10 -07:00
2008-10-26 14:42:57 -07:00
2008-09-15 23:11:35 -07:00
2009-04-17 20:59:01 -07:00
2008-07-16 14:03:24 -07:00
2007-06-07 00:04:01 -07:00
2008-07-25 17:09:38 -07:00
2008-02-25 23:57:35 -08:00
2008-08-16 02:32:36 -07:00
2008-07-15 19:09:46 -07:00
2008-08-05 21:21:08 -07:00
2008-07-13 14:12:48 -07:00
2008-07-13 14:12:48 -07:00
2008-07-13 14:12:48 -07:00
2008-09-12 16:18:47 -07:00
2008-07-13 14:12:48 -07:00
2008-08-21 22:18:21 -07:00
2008-07-19 11:28:06 -07:00
2008-08-04 21:52:08 -07:00
2008-07-21 19:11:50 -07:00
2008-07-21 19:11:50 -07:00
2009-02-03 22:11:44 -08:00
2007-12-13 23:04:26 -08:00
2008-02-09 23:16:51 -08:00
2008-02-25 23:57:35 -08:00
2008-07-13 14:12:48 -07:00
2008-08-06 13:50:48 -07:00
2008-08-06 13:50:48 -07:00
2007-06-07 00:04:01 -07:00
2008-10-26 14:42:57 -07:00
2008-07-21 19:11:50 -07:00
2008-12-19 19:27:35 -08:00
2008-07-21 19:11:50 -07:00
2008-08-24 23:28:02 -07:00
2007-11-09 21:14:10 -08:00
2008-10-06 00:37:30 -07:00
2008-07-21 19:11:50 -07:00
2008-07-25 17:09:38 -07:00
2008-07-21 19:11:50 -07:00
2008-07-21 19:11:50 -07:00
2008-03-02 15:11:07 -08:00
2005-11-02 16:50:58 -08:00
2006-03-25 16:35:43 -08:00
2007-05-01 02:59:08 -07:00
2008-07-30 11:42:01 -07: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 "man git-commandname" for documentation of each command.
CVS users may also want to read Documentation/cvs-migration.txt.

Many Git online resources are accessible from http://git.or.cz/
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 582 MiB
Languages
C 50.5%
Shell 38.7%
Perl 4.5%
Tcl 3.2%
Python 0.8%
Other 2.1%