Michael Montalbo 84532f64fd diff: extract a line-range diff helper for reuse
builtin_diff() open-codes the line-range filter setup and teardown
around its xdi_diff_outf() call: zero the struct, point it at the
output callback, inflate ctxlen to the largest range span so each range
yields a single xdiff hunk, run the diff, flush the trailing range
hunk, and release the buffer.  The upcoming -L stat and check formats
need the same sequence.

Extract line_range_filter_init() for the setup and a
line_range_filter_diff() helper that prepares the xdiff config the
filter needs, runs an initialized filter through xdi_diff_outf(),
flushes the final range hunk, and releases it, returning the latched
error.  The helper inflates ctxlen to the largest range span so each
range yields a single xdiff hunk, and clears XDL_EMIT_NO_HUNK_HDR so
the hunk headers the filter seeds its position from are always emitted.
Folding both into the helper keeps these invariants, which the filter's
position tracking relies on, in a single place for every consumer.
builtin_diff() now does init + line_range_filter_diff(); the next two
patches reuse them in builtin_diffstat() and builtin_checkdiff()
instead of repeating the boilerplate.

No behavior change: builtin_diff() leaves XDL_EMIT_NO_HUNK_HDR unset,
so clearing it is a no-op until the suppressing consumers arrive.

Signed-off-by: Michael Montalbo <mmontalbo@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2026-06-18 11:52:28 -07:00
2026-05-21 12:06:48 +09:00
2026-05-31 10:00:38 +09:00
2026-06-09 10:04:51 +09:00
2026-05-27 14:15:46 +09:00
2026-04-09 17:25:36 -07:00
2026-05-21 12:06:48 +09:00
2026-05-21 22:31:38 +09:00
2026-06-09 10:04:50 +09:00
2026-03-23 09:20:29 -07:00
2026-05-21 12:06:48 +09:00
2026-05-29 05:11:03 +09:00
2026-05-14 15:59:25 +09:00
2026-03-23 08:33:10 -07:00
2026-04-19 19:01:39 -07:00
2026-05-14 15:59:25 +09:00
2026-05-14 15:59:25 +09:00
2026-04-10 07:58:54 -07:00
2026-06-11 04:31:17 -07:00
2026-05-15 04:50:45 +09:00
2026-05-31 10:00:38 +09:00
2026-04-09 17:25:36 -07:00
2026-05-31 10:00:38 +09:00
2026-03-31 20:43:14 -07:00
2026-05-27 14:15:46 +09:00
2026-05-27 14:15:45 +09:00
2026-05-27 14:15:45 +09:00
2026-05-15 04:50:45 +09:00
2026-05-15 04:50:45 +09:00
2026-05-24 18:41:07 +09:00
2026-03-26 09:38:06 -07:00
2026-03-26 09:38:06 -07:00
2026-06-09 10:04:50 +09:00
2026-05-19 12:14:03 +09:00
2026-05-19 12:14:03 +09:00
2026-03-09 14:36:55 -07:00
2026-03-31 20:43:14 -07:00
2026-06-09 10:04:50 +09:00
2026-03-23 21:27:17 -07:00
2026-05-21 12:42:11 +09:00
2026-06-09 10:04:50 +09:00
2026-06-09 10:04:50 +09:00
2026-06-07 23:58:24 +09:00
2026-06-11 04:31:17 -07:00
2026-05-31 10:00:38 +09:00
2026-06-09 10:04:50 +09:00
2026-06-09 10:04:50 +09:00
2026-05-13 00:48:42 +09:00
2026-05-06 09:48:28 +09:00
2026-05-06 09:48:28 +09:00
2026-03-31 20:43:14 -07:00

Build status

Git - fast, scalable, distributed revision control system

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 version 2 (some parts of it are under different licenses, compatible with the GPLv2). It was originally written by Linus Torvalds with help of a group of hackers around the net.

Please read the file INSTALL for installation instructions.

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

See Documentation/gittutorial.adoc to get started, then see Documentation/giteveryday.adoc for a useful minimum set of commands, and Documentation/git-<commandname>.adoc 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.adoc (man gitcvs-migration or git help cvs-migration if git is installed).

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 (read Documentation/SubmittingPatches for instructions on patch submission and Documentation/CodingGuidelines).

Those wishing to help with error message, usage and informational message string translations (localization l10) should see po/README.md (a po file is a Portable Object file that holds the translations).

To subscribe to the list, send an email to git+subscribe@vger.kernel.org (see https://subspace.kernel.org/subscribing.html for details). The mailing list archives are available at https://lore.kernel.org/git/, https://marc.info/?l=git and other archival sites.

Issues which are security relevant should be disclosed privately to the Git Security mailing list git-security@googlegroups.com.

The maintainer frequently sends the "What's cooking" reports that list the current status of various development topics to the mailing list. The discussion following them give a good reference for project status, development direction and remaining tasks.

The name "git" was given by Linus Torvalds when he wrote the very first version. He described the tool as "the stupid content tracker" and the name as (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
Description
A fork of Git containing Windows-specific patches.
Readme 502 MiB
2025-08-19 03:50:05 -05:00
Languages
C 50.2%
Shell 39.2%
Perl 4.3%
Tcl 3%
Python 0.8%
Other 2.2%