Junio C Hamano 2fa04cebfb format-patch: move range/inter diff at the end of a single patch output
When running "format-patch" on a multiple patch series, the output
coming from "--interdiff" and "--range-diff" options is inserted
after the "shortlog" list of commits and the overall diffstat.

The idea is that shortlog/diffstat are shorter and with denser
information content, which gives a better overview before the
readers dive into more details of range/inter diff.

When working on a single patch, however, we stuff the inter/range
diff output before the actual patch, next to the diffstat.  This
pushes down the patch text way down with inter/range diff output,
distracting readers.

Move the inter/range diff output to the very end of the output,
after all the patch text is shown.

As the inter/range diff is no longer part of the commentary block
(i.e., what comes after the log message and "---", but before the
patch text), stop producing "---" in the function that generates
them.  But to separate it out visually (note: this is not needed
to help tools like "git apply" that pay attention to the hunk
headers to figure out the length of the hunks), add an extra blank
line between the end of the patch text and the inter/range diff.

Signed-off-by: Junio C Hamano <gitster@pobox.com>
2024-05-24 16:26:57 -07:00
2024-05-23 11:04:29 -07:00
2023-12-14 14:38:07 -08:00
2024-05-23 11:04:27 -07:00
2023-11-26 10:07:06 +09:00
2023-11-26 10:10:48 +09:00
2024-05-03 10:36:59 -07:00
2024-04-25 10:34:24 -07:00
2024-02-12 09:32:41 -08:00
2024-03-28 14:13:50 -07:00
2023-12-26 12:04:32 -08:00
2023-11-26 10:10:48 +09:00
2024-03-28 14:13:50 -07:00
2024-01-23 10:40:10 -08:00
2023-11-26 10:10:48 +09:00
2024-03-28 14:13:50 -07:00
2024-02-12 09:32:41 -08:00
2024-04-19 12:38:46 +02:00
2024-04-19 12:38:42 +02:00
2024-04-05 15:21:14 -07:00
2024-04-05 15:21:14 -07:00
2024-04-29 20:42:30 +02:00
2024-04-29 20:42:30 +02:00
2024-04-19 12:38:50 +02:00
2024-04-29 20:42:30 +02:00
2024-04-19 12:38:50 +02:00
2023-11-26 10:07:05 +09:00
2024-04-30 14:52:20 -07:00
2024-05-03 10:36:59 -07:00
2023-11-26 10:07:05 +09:00
2024-04-19 12:38:46 +02:00
2024-03-28 14:13:50 -07:00
2024-04-19 12:38:50 +02: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
2023-11-26 10:07:05 +09:00
2024-05-23 11:04:27 -07:00
2024-02-26 09:35:40 -08:00
2024-03-28 14:13:50 -07:00
2024-04-23 11:52:40 -07:00
2024-02-26 15:34:01 -08:00
2024-02-26 15:34:01 -08:00
2024-03-28 14:13:50 -07:00
2024-03-28 14:13:50 -07:00
2024-03-28 14:13:50 -07:00
2024-04-29 20:42:30 +02:00
2024-04-29 20:42:30 +02:00
2023-11-26 10:07:05 +09:00
2024-04-29 20:42:30 +02:00
2024-04-05 15:21:14 -07:00
2024-04-30 14:52:20 -07:00
2024-05-13 18:29:15 -07:00
2024-04-23 11:52:41 -07:00
2024-04-29 20:42:30 +02:00
2023-11-26 10:07:05 +09:00
2024-03-02 11:12:16 -08:00
2023-12-27 14:52:24 -08:00
2024-04-05 10:49:49 -07:00
2024-04-19 12:38:37 +02:00
2023-11-26 10:07:05 +09:00
2024-05-23 11:04:27 -07:00
2024-05-23 11:04:27 -07:00
2024-03-28 14:13:50 -07:00
2024-03-28 14:13:50 -07:00
2024-03-28 14:13:50 -07:00
2024-04-05 15:16:27 -07:00
2023-11-26 10:07:05 +09:00
2023-11-26 10:07:05 +09: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
Git Source Code Mirror - This is a publish-only repository but pull requests can be turned into patches to the mailing list via GitGitGadget (https://gitgitgadget.github.io/). Please follow Documentation/SubmittingPatches procedure for any of your improvements.
Readme 734 MiB
Languages
C 50.5%
Shell 38.7%
Perl 4.5%
Tcl 3.2%
Python 0.8%
Other 2.1%