Jeff King c5e358d073 sequencer: don't say BUG on bogus input
When cherry-picking a single commit, we go through a special
code path that avoids creating a sequencer todo list at all.
This path expects our revision parsing to turn up exactly
one commit, and dies with a BUG if it doesn't.

But it's actually quite easy to fool. For example:

  $ git cherry-pick --author=no.such.person HEAD
  error: BUG: expected exactly one commit from walk
  fatal: cherry-pick failed

This isn't a bug; it's just bogus input.

The condition to trigger this message actually has two
parts:

  1. We saw no commits. That's the case in the example
     above. Let's drop the "BUG" here to make it clear that
     the input is the problem. And let's also use the phrase
     "empty commit set passed", which matches what we say
     when we do a real revision walk and it turns up empty.

  2. We saw more than one commit. That one _should_ be
     impossible to trigger, since we fed at most one tip and
     provided the no_walk option (and we'll have already
     expanded options like "--branches" that can turn into
     multiple tips). If this ever triggers, it's an
     indication that the conditional added by 7acaaac275
     (revert: allow single-pick in the middle of cherry-pick
     sequence, 2011-12-10) needs to more carefully define
     the single-pick case.

     So this can remain a bug, but we'll upgrade it to use
     the BUG() macro, which would make it easier to detect
     and analyze if it does trigger.

Signed-off-by: Jeff King <peff@peff.net>
Acked-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2018-07-11 08:37:59 -07: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
2017-09-29 11:23:43 +09: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%