Jeff King 6b93506696 tempfile: robustify cleanup handler
We may call remove_tempfiles() from an atexit handler, or
from a signal handler. In the latter case we must take care
to avoid functions which may deadlock if the process is in
an unknown state, including looking at any stdio handles
(which may be in the middle of doing I/O and locked) or
calling malloc() or free().

The current implementation calls delete_tempfile(). We unset
the tempfile's stdio handle (if any) to avoid deadlocking
there. But delete_tempfile() still calls unlink_or_warn(),
which can deadlock writing to stderr if the unlink fails.

Since delete_tempfile() isn't very long, let's just
open-code our own simple conservative version of the same
thing.  Notably:

  1. The "skip_fclose" flag is now called "in_signal_handler",
     because it should inform more decisions than just the
     fclose handling.

  2. We can replace close_tempfile() with just close(fd).
     That skips the fclose() question altogether. This is
     fine for the atexit() case, too; there's no point
     flushing data to a file which we're about to delete
     anyway.

  3. We can choose between unlink/unlink_or_warn based on
     whether it's safe to use stderr.

  4. We can replace the deactivate_tempfile() call with a
     simple setting of the active flag. There's no need to
     do any further cleanup since we know the program is
     exiting.  And even though the current deactivation code
     is safe in a signal handler, this frees us up in future
     patches to make non-signal deactivation more
     complicated (e.g., by freeing resources).

  5. There's no need to remove items from the tempfile_list.
     The "active" flag is the ultimate answer to whether an
     entry has been handled or not. Manipulating the list
     just introduces more chance of recursive signals
     stomping on each other, and the whole list will go away
     when the program exits anyway. Less is more.

Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2017-09-06 17:19:53 +09:00
2017-09-06 13:11:25 +09:00
2017-09-06 13:15:24 +09:00
2017-07-10 14:24:36 -07:00
2017-08-22 10:29:07 -07:00
2017-07-06 18:14:44 -07:00
2017-08-26 22:55:06 -07:00
2017-03-24 13:31:01 -07:00
2017-06-27 10:35:49 -07:00
2017-06-24 14:28:41 -07:00
2017-08-26 22:55:05 -07:00
2017-06-24 14:28:41 -07:00
2017-06-24 14:28:41 -07:00
2017-07-05 13:53:12 -07:00
2017-03-13 15:28:54 -07:00
2017-07-31 13:05:15 -07:00
2017-05-25 13:08:23 +09:00
2017-05-08 15:12:57 +09:00
2017-05-08 15:12:57 +09:00
2017-08-03 11:08:10 -07:00
2017-05-29 12:34:43 +09:00
2017-05-02 10:46:41 +09:00
2017-08-26 22:55:09 -07:00
2017-01-25 14:42:37 -08:00
2017-08-18 12:41:06 -07:00
2017-09-06 13:11:25 +09:00
2017-08-26 22:55:08 -07:00
2017-08-26 22:55:08 -07:00
2017-06-22 14:15:20 -07:00
2017-08-04 12:40:37 -07:00
2017-08-26 22:55:05 -07:00
2017-08-26 22:55:05 -07:00
2017-06-24 14:28:41 -07:00
2017-06-24 14:28:41 -07:00
2017-06-22 14:15:21 -07:00
2017-06-24 14:28:41 -07:00
2017-03-31 08:33:56 -07:00
2017-03-31 08:33:56 -07:00
2016-07-01 12:44:57 -07:00
2016-07-01 12:44:57 -07:00
2017-08-23 14:36:03 -07:00
2017-08-23 15:12:07 -07:00
2017-08-23 15:12:07 -07:00
2017-08-26 22:55:09 -07:00
2017-06-24 14:28:41 -07:00
2017-07-12 15:18:23 -07:00
2017-06-24 14:28:41 -07:00
2017-01-30 14:17:00 -08:00
2017-06-24 14:28:41 -07:00
2016-12-07 11:31:59 -08:00
2017-06-24 14:28:41 -07:00
2017-06-27 10:35:49 -07:00
2017-08-26 22:55:09 -07:00
2016-07-29 11:05:07 -07:00
2016-07-29 11:05:07 -07:00
2017-06-24 14:28:41 -07:00
2017-02-08 15:39:55 -08:00
2017-01-30 14:17:00 -08:00
2017-08-23 15:12:07 -07:00
2017-08-23 15:12:07 -07:00
2017-08-22 10:29:03 -07:00
2017-05-29 12:34:43 +09:00
2017-06-24 14:28:41 -07:00
2017-06-27 10:35:49 -07:00
2017-08-26 22:55:04 -07:00
2016-07-28 11:26:03 -07:00
2016-07-28 11:26:03 -07:00
2017-07-17 14:54:56 -07:00
2017-08-26 22:55:09 -07:00
2017-06-27 10:35:49 -07:00
2017-08-23 14:36:03 -07:00
2017-08-11 13:27:01 -07:00
2017-08-23 15:12:07 -07:00
2017-08-02 15:45:20 -07:00
2017-06-27 10:35:49 -07:00
2017-03-31 08:33:56 -07:00
2017-09-06 13:11:25 +09:00
2017-03-31 08:33:56 -07:00
2017-05-22 10:20:46 +09:00
2017-05-22 10:20:46 +09:00
2017-06-24 14:28:41 -07:00
2017-08-23 15:12:06 -07:00
2017-07-17 14:54:56 -07:00
2017-09-06 17:19:53 +09:00
2016-08-05 09:28:17 -07:00
2017-08-26 22:55:04 -07:00
2017-08-26 22:55:04 -07:00
2017-06-24 14:28:41 -07:00
2017-06-24 14:28:41 -07:00
2017-06-24 14:28:41 -07:00
2016-09-26 18:16:23 -07:00
2017-06-24 14:28:41 -07:00
2017-06-24 14:28:41 -07:00

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-.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). 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 https://public-inbox.org/git/, http://marc.info/?l=git and other archival sites.

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 720 MiB
Languages
C 50.5%
Shell 38.8%
Perl 4.4%
Tcl 3.2%
Python 0.8%
Other 2.1%