Jeff King 862e80a413 ident: handle NULL email when complaining of empty name
If we see an empty name, we complain about and mention the
matching email in the error message (to give it some
context). However, the "email" pointer may be NULL here if
we were planning to fill it in later from ident_default_email().

This was broken by 59f929596 (fmt_ident: refactor strictness
checks, 2016-02-04). Prior to that commit, we would look up
the default name and email before doing any other actions.
So one solution would be to go back to that.

However, we can't just do so blindly. The logic for handling
the "!email" condition has grown since then. In particular,
looking up the default email can die if getpwuid() fails,
but there are other errors that should take precedence.
Commit 734c7789a (ident: check for useConfigOnly before
auto-detection of name/email, 2016-03-30) reordered the
checks so that we prefer the error message for
useConfigOnly.

Instead, we can observe that while the name-handling depends
on "email" being set, the reverse is not true. So we can
simply set up the email variable first.

This does mean that if both are bogus, we'll complain about
the email before the name. But between the two, there is no
reason to prefer one over the other.

Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2017-02-23 12:46:00 -08:00
2016-05-10 11:19:07 -07:00
2017-02-02 13:21:27 -08:00
2016-02-22 14:51:09 -08:00
2016-10-20 09:33:17 -07:00
2016-10-17 13:25:20 -07:00
2016-09-26 17:46:44 -07:00
2016-02-22 14:51:09 -08:00
2014-07-28 10:14:33 -07:00
2016-11-22 13:55:20 -08:00
2016-11-22 13:55:20 -08:00
2016-02-22 14:50:32 -08:00
2016-02-22 14:50:32 -08:00
2016-09-29 15:42:18 -07:00
2016-05-09 12:29:08 -07:00
2016-02-22 14:51:09 -08:00
2016-08-12 09:47:37 -07:00
2016-10-10 14:03:50 -07:00
2016-10-31 13:15:21 -07:00
2016-05-09 12:29:08 -07:00
2014-12-12 14:31:42 -08:00
2016-07-27 14:15:51 -07:00
2015-11-20 08:02:05 -05:00
2014-03-31 15:29:27 -07:00
2016-10-27 14:58:50 -07:00
2016-09-29 15:42:18 -07:00
2016-05-09 12:29:08 -07:00
2016-07-01 12:44:57 -07:00
2016-07-01 12:44:57 -07:00
2016-10-14 01:36:12 +00:00
2017-01-17 15:19:11 -08:00
2014-07-07 13:56:38 -07:00
2016-09-29 15:42:18 -07:00
2016-02-22 14:51:09 -08:00
2016-09-29 15:42:18 -07:00
2016-05-17 14:38:32 -07:00
2014-10-20 12:23:48 -07:00
2016-07-29 11:05:07 -07:00
2016-07-29 11:05:07 -07:00
2016-09-26 16:09:18 -07:00
2015-11-20 08:02:05 -05:00
2016-06-13 14:38:16 -07:00
2016-09-29 15:42:18 -07:00
2016-09-25 16:44:13 -07:00
2016-09-29 15:42:18 -07:00
2016-10-17 13:25:21 -07:00
2016-10-28 09:01:23 -07:00
2016-07-28 11:26:03 -07:00
2016-07-28 11:26:03 -07:00
2016-05-09 12:29:08 -07:00
2015-09-25 08:54:54 -07:00
2016-10-26 13:14:45 -07:00
2016-10-10 14:03:50 -07:00
2017-01-17 15:19:11 -08:00
2016-04-25 15:17:15 -07:00
2016-07-14 15:50:41 -07:00
2016-09-29 15:42:18 -07:00
2016-10-10 14:03:46 -07:00
2016-07-01 15:09:10 -07:00
2014-06-13 11:49:40 -07:00
2016-09-29 15:42:18 -07:00
2014-12-22 12:27:30 -08:00
2016-08-05 09:28:17 -07:00
2016-10-31 13:15:22 -07:00
2016-10-27 14:58:48 -07:00
2016-09-29 15:42:18 -07:00
2014-09-02 13:28:44 -07:00
2016-09-19 13:47:18 -07:00
2016-02-22 10:40:35 -08:00
2016-09-26 18:16:23 -07:00
2016-11-28 13:18:51 -08:00
2016-11-28 13:18:51 -08:00
2016-10-27 14:58:50 -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 http://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 582 MiB
Languages
C 50.5%
Shell 38.7%
Perl 4.5%
Tcl 3.2%
Python 0.8%
Other 2.1%