Junio C Hamano 5cdb38458e 2.36 show regression fix
This only surfaced as a regression after 2.36 release, but the
breakage was already there with us for at least a year.

e900d494 (diff: add an API for deferred freeing, 2021-02-11)
introduced a mechanism to delay freeing resources held in
diff_options struct that need to be kept as long as the struct will
be reused to compute diff.  "git log -p" was taught to utilize the
mechanism but it was done with an incorrect assumption that the
underlying helper function, cmd_log_walk(), is called only once,
and it is OK to do the freeing at the end of it.

Alas, for "git show A B", the function is called once for each
commit given, so it is not OK to free the resources until we finish
calling it for all the commits given from the command line.

During 2.36 release cycle, we started clearing the <pathspec> as
part of this freeing, which made the bug a lot more visible.

Fix this breakage by tweaking how cmd_log_walk() frees the resources
at the end and using a variant of it that does not immediately free
the resources to show each commit object from the command line in
"git show".

Protect the fix with a few new tests.

Reported-by: Daniel Li <dan@danielyli.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2022-04-29 22:31:17 -07:00
2021-12-15 09:39:49 -08:00
2022-04-29 22:31:17 -07:00
2021-03-13 16:00:09 -08:00
2021-03-13 16:00:09 -08:00
2022-01-23 09:40:52 +01:00
2022-04-29 22:31:17 -07:00
2021-12-15 09:39:47 -08:00
2021-08-12 14:00:52 -07:00
2022-01-07 15:19:34 -08:00
2022-02-16 15:14:29 -08:00
2022-02-25 15:47:36 -08:00
2021-05-07 12:47:41 +09:00
2022-01-07 15:19:34 -08:00
2021-12-10 14:35:12 -08:00
2021-01-23 17:14:07 -08:00
2022-02-25 15:47:36 -08:00
2021-07-13 16:52:50 -07:00
2022-01-07 15:19:34 -08:00
2021-03-13 16:00:09 -08:00
2022-01-05 14:01:28 -08:00
2022-02-25 15:47:36 -08:00
2022-01-05 14:01:31 -08:00
2021-03-13 16:00:09 -08:00
2022-02-25 15:47:36 -08:00
2022-01-03 16:24:15 -08:00
2021-09-23 13:44:48 -07:00
2022-01-28 16:48:42 -08:00
2022-02-25 15:47:36 -08:00
2022-02-25 15:47:36 -08:00
2021-03-13 16:00:09 -08:00
2021-03-13 16:00:09 -08:00
2021-03-13 16:00:09 -08:00
2022-02-16 15:14:29 -08:00
2022-01-27 12:07:53 -08:00
2022-02-25 15:47:36 -08:00
2021-03-13 16:00:09 -08:00
2021-04-27 16:31:39 +09:00
2022-01-03 16:24:15 -08:00
2022-01-03 16:24:15 -08:00
2022-01-03 16:24:15 -08:00
2021-03-13 16:00:09 -08:00
2021-03-13 16:00:09 -08:00
2021-09-20 15:20:40 -07:00
2021-08-24 15:32:37 -07:00
2022-02-25 15:47:36 -08:00
2022-01-03 16:24:15 -08:00
2022-02-25 15:47:36 -08:00
2022-02-23 16:58:03 -08:00
2021-10-25 16:06:58 -07:00
2022-01-05 14:01:28 -08:00
2021-05-04 11:52:02 +09:00
2021-05-04 11:52:02 +09:00
2021-12-15 09:39:52 -08:00
2022-01-05 14:01:28 -08: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 with just "subscribe git" in the body to majordomo@vger.kernel.org (not the Git list). The mailing list archives are available at https://lore.kernel.org/git/, http://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 279 MiB
Languages
C 50.5%
Shell 38.7%
Perl 4.5%
Tcl 3.2%
Python 0.8%
Other 2.1%