Justin Tobler 5bd10b2adc builtin: introduce diff-pairs command
Through git-diff(1), a single diff can be generated from a pair of blob
revisions directly. Unfortunately, there is not a mechanism to compute
batches of specific file pair diffs in a single process. Such a feature
is particularly useful on the server-side where diffing between a large
set of changes is not feasible all at once due to timeout concerns.

To facilitate this, introduce git-diff-pairs(1) which acts as a backend
passing its NUL-terminated raw diff format input from stdin through diff
machinery to produce various forms of output such as patch or raw.

The raw format was originally designed as an interchange format and
represents the contents of the diff_queued_diff list making it possible
to break the diff pipeline into separate stages. For example,
git-diff-tree(1) can be used as a frontend to compute file pairs to
queue and feed its raw output to git-diff-pairs(1) to compute patches.
With this, batches of diffs can be progressively generated without
having to recompute renames or retrieve object context. Something like
the following:

	git diff-tree -r -z -M $old $new |
	git diff-pairs -p -z

should generate the same output as `git diff-tree -p -M`. Furthermore,
each line of raw diff formatted input can also be individually fed to a
separate git-diff-pairs(1) process and still produce the same output.

Based-on-patch-by: Jeff King <peff@peff.net>
Signed-off-by: Justin Tobler <jltobler@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2025-03-03 08:17:47 -08:00
2025-02-06 14:56:45 -08:00
2024-12-15 17:54:33 -08:00
2025-01-08 08:05:39 -08:00
2023-11-26 10:07:06 +09:00
2025-03-03 08:17:47 -08:00
2024-09-20 14:40:41 -07:00
2024-09-06 09:31:15 -07:00
2024-12-18 10:44:30 -08:00
2024-12-23 09:32:11 -08:00
2024-12-23 09:32:11 -08:00
2024-09-23 10:35:07 -07:00
2025-02-10 10:18:31 -08:00
2024-09-16 10:46:00 -07:00
2024-06-14 10:26:33 -07:00
2024-06-14 10:26:33 -07:00
2024-01-23 10:40:10 -08:00
2024-06-14 10:26:33 -07:00
2024-06-14 10:26:33 -07:00
2025-01-21 08:44:54 -08:00
2025-01-21 08:44:54 -08:00
2025-02-10 10:18:31 -08:00
2024-12-23 09:32:11 -08:00
2024-04-05 15:21:14 -07:00
2024-12-18 10:44:31 -08:00
2024-12-18 10:44:31 -08:00
2025-02-03 16:12:42 -08:00
2025-02-03 16:12:42 -08:00
2024-12-18 10:44:30 -08:00
2023-04-17 21:15:56 +02:00
2024-10-23 16:16:36 -04:00
2025-02-06 14:56:45 -08:00
2024-10-23 16:16:36 -04:00
2024-10-23 16:16:36 -04:00
2024-09-19 13:46:00 -07:00
2025-02-26 08:55:18 -08:00
2025-03-03 08:17:47 -08:00
2024-12-18 10:44:31 -08:00
2023-11-26 10:07:05 +09:00
2023-06-28 14:06:39 -07:00
2025-01-31 10:06:10 -08:00
2023-06-28 14:06:39 -07:00
2024-10-23 16:16:36 -04:00
2023-11-26 10:07:05 +09:00
2023-11-26 10:07:05 +09:00
2023-11-26 10:07:05 +09:00
2024-06-14 10:26:33 -07:00
2024-12-18 10:44:31 -08:00
2024-12-18 10:44:31 -08:00
2025-03-03 08:17:47 -08:00
2024-07-08 14:53:10 -07:00
2025-02-06 14:56:45 -08:00
2024-12-23 09:32:11 -08:00
2024-02-26 15:34:01 -08:00
2024-07-08 14:53:10 -07:00
2024-06-14 10:26:33 -07:00
2024-10-21 16:05:04 -04:00
2024-06-14 10:26:33 -07:00
2025-01-21 08:44:54 -08:00
2025-02-10 10:18:31 -08:00
2024-12-18 10:44:30 -08:00
2024-12-18 10:44:30 -08:00
2024-05-24 11:40:42 -07:00
2024-05-24 11:40:42 -07:00
2025-02-03 16:12:42 -08:00
2025-02-03 16:12:42 -08:00
2024-12-23 09:32:11 -08:00
2024-12-18 10:44:30 -08:00
2024-12-18 10:44:30 -08:00
2023-11-26 10:07:05 +09:00
2024-05-11 17:22:17 +02:00
2024-09-19 13:46:01 -07:00
2024-04-05 15:21:14 -07:00
2024-06-14 10:26:33 -07:00
2024-09-19 13:46:12 -07:00
2024-09-19 13:46:12 -07:00
2025-02-06 14:56:45 -08:00
2024-12-18 10:44:30 -08:00
2024-12-18 10:44:30 -08:00
2023-11-26 10:07:05 +09:00
2024-12-27 08:12:40 -08:00
2024-09-30 11:23:03 -07:00
2024-06-14 10:26:33 -07:00
2023-09-15 17:08:46 -07:00
2025-01-13 12:55:26 -08:00
2025-01-13 12:55:26 -08:00
2024-12-23 09:32:11 -08:00
2024-12-23 09:32:11 -08:00
2024-05-17 10:33:39 -07:00
2024-12-18 10:44:30 -08:00
2024-12-18 10:44:30 -08:00
2024-06-14 10:26:33 -07:00
2025-02-06 14:56:45 -08:00
2023-06-28 14:06:39 -07:00
2025-01-17 13:30:02 -08:00
2024-12-18 10:44:30 -08:00
2023-04-04 14:28:27 -07:00
2024-06-14 10:26:33 -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.txt to get started, then see Documentation/giteveryday.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).

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
No description provided
Readme 581 MiB
Languages
C 50.5%
Shell 38.7%
Perl 4.5%
Tcl 3.2%
Python 0.8%
Other 2.1%