Nguyễn Thái Ngọc Duy e34de73c56 upload-pack: reject shallow requests that would return nothing
Shallow clones with --shallow-since or --shalow-exclude work by
running rev-list to get all reachable commits, then draw a boundary
between reachable and unreachable and send "shallow" requests based on
that.

The code does miss one corner case: if rev-list returns nothing, we'll
have no border and we'll send no shallow requests back to the client
(i.e. no history cuts). This essentially means a full clone (or a full
branch if the client requests just one branch). One example is the
oldest commit is older than what is specified by --shallow-since.

To avoid this, if rev-list returns nothing, we abort the clone/fetch.
The user could adjust their request (e.g. --shallow-since further back
in the past) and retry.

Another possible option for this case is to fall back to a default
depth (like depth 1). But I don't like too much magic that way because
we may return something unexpected to the user. If they request
"history since 2008" and we return a single depth at 2000, that might
break stuff for them. It is better to tell them that something is
wrong and let them take the best course of action.

Note that we need to die() in get_shallow_commits_by_rev_list()
instead of just checking for empty result from its caller
deepen_by_rev_list() and handling the error there. The reason is,
empty result could be a valid case: if you have commits in year 2013
and you request --shallow-since=year.2000 then you should get a full
clone (i.e. empty result).

Reported-by: Andreas Krey <a.krey@gmx.de>
Signed-off-by: Nguyễn Thái Ngọc Duy <pclouds@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2018-06-04 11:03:10 +09:00
2018-05-22 14:18:06 +09:00
2017-11-21 14:07:50 +09:00
2018-05-22 14:18:51 +09:00
2018-01-15 07:47:30 +01:00
2018-05-22 14:18:06 +09:00
2017-11-15 12:14:28 +09:00
2017-12-27 11:16:25 -08:00
2017-12-27 11:16:25 -08:00
2018-05-22 14:18:06 +09:00
2017-12-04 09:38:30 -08:00
2017-10-24 10:19:06 +09:00
2017-12-08 09:16:27 -08:00
2017-12-08 09:16:27 -08:00
2017-12-13 13:28:54 -08:00
2017-11-28 10:40:04 +09:00
2017-12-27 11:16:21 -08:00
2017-12-27 11:16:21 -08:00
2017-11-21 14:07:50 +09:00
2018-05-22 14:18:06 +09:00
2018-05-22 14:18:06 +09:00
2018-05-22 14:18:51 +09:00
2017-11-28 13:41:50 +09:00
2017-12-13 13:28:54 -08:00
2017-11-21 14:05:30 +09:00
2017-11-01 10:35:39 +09:00
2017-08-23 15:12:07 -07:00
2018-01-19 13:06:57 -08:00
2017-12-28 14:08:50 -08:00
2017-09-06 17:19:54 +09:00
2017-11-09 14:31:27 +09:00
2017-12-28 13:50:05 -08:00
2017-12-27 12:28:06 -08:00
2017-11-22 14:11:56 +09:00
2017-08-23 15:12:07 -07:00
2017-08-22 10:29:03 -07:00
2018-05-22 14:15:14 +09:00
2017-12-13 11:14:25 -08:00
2017-12-06 09:23:44 -08:00
2017-10-17 10:51:29 +09:00
2017-12-12 10:41:15 -08:00
2017-12-19 11:33:55 -08:00
2018-05-22 14:18:06 +09:00
2018-05-22 14:18:51 +09:00
2017-09-25 15:24:06 +09:00
2018-02-22 12:15:25 -08:00
2017-12-19 11:33:58 -08:00
2018-05-22 14:18:06 +09:00
2018-05-22 14:18:06 +09:00
2017-08-26 22:55:04 -07:00
2017-12-06 09:23:44 -08:00
2018-05-22 14:15:14 +09:00
2018-05-21 23:50:11 -04:00
2017-11-06 14:24:27 +09: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 279 MiB
Languages
C 50.5%
Shell 38.7%
Perl 4.5%
Tcl 3.2%
Python 0.8%
Other 2.1%