Johannes Schindelin 5ee4ef8bda t3418: decouple test cases from a previous rebase -p test case
It is in general a good idea for regression test cases to be as
independent of each other as possible (with the one exception of an
initial `setup` test case, which is only a test case in Git's test suite
because it does not have a notion of a fixture or setup).

This patch addresses one particular instance of this principle being
violated: a few test cases in t3418-rebase-continue.sh depend on a side
effect of a test case that verifies a specific `rebase -p` behavior. The
later test cases should, however, still succeed even if the `rebase -p`
test case is skipped.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2018-11-02 11:27:30 +09:00
2018-10-19 09:21:28 +09:00
2018-10-30 15:44:45 +09:00
2018-08-02 13:54:58 -07:00
2018-10-16 16:16:01 +09:00
2018-08-20 12:41:32 -07:00
2018-08-20 11:33:53 -07:00
2018-10-19 13:34:02 +09:00
2018-08-20 12:41:32 -07:00
2018-09-12 15:15:34 -07:00
2018-09-12 15:15:34 -07:00
2018-07-26 10:12:51 -07:00
2018-10-19 13:34:02 +09:00
2018-10-19 13:34:02 +09:00
2018-10-19 13:34:02 +09:00
2018-10-26 14:22:10 +09:00
2018-03-30 12:49:57 -07:00
2018-03-30 12:49:57 -07:00
2018-10-19 13:34:02 +09:00
2018-10-30 15:43:47 +09:00
2018-05-08 15:59:17 +09:00
2018-10-19 13:34:03 +09:00
2018-08-29 11:32:49 -07:00
2018-08-20 12:41:32 -07:00
2017-12-08 09:16:27 -08:00
2017-12-08 09:16:27 -08:00
2018-10-19 13:34:02 +09:00
2018-10-19 13:34:02 +09:00
2018-10-19 13:34:02 +09:00
2018-10-19 13:34:02 +09:00
2018-09-17 13:53:57 -07:00
2018-05-08 15:59:17 +09:00
2018-09-17 13:53:57 -07:00
2018-10-30 15:43:48 +09:00
2018-05-08 15:59:34 +09:00
2018-09-27 11:52:33 -07:00
2018-10-26 14:22:13 +09:00
2018-08-20 11:33:50 -07:00
2018-07-16 14:27:39 -07:00
2018-10-19 13:34:02 +09:00
2018-08-29 11:32:49 -07:00
2018-05-30 21:51:28 +09:00
2018-10-30 15:43:39 +09:00
2018-10-19 13:34:02 +09:00
2018-09-17 13:53:57 -07:00
2018-08-29 13:05:35 -07:00
2018-10-26 14:22:14 +09:00
2018-10-19 13:34:02 +09:00
2018-10-19 13:34:02 +09:00
2018-08-29 11:32:49 -07:00
2018-08-20 15:31:40 -07:00
2018-08-29 11:32:49 -07:00
2018-09-17 13:53:52 -07:00
2018-10-04 11:12:14 -07:00
2018-10-04 11:12:14 -07:00
2018-02-02 11:28:41 -08:00
2018-06-01 15:06:37 +09:00
2018-10-19 13:34:02 +09:00
2018-07-18 12:20:28 -07:00
2018-09-17 13:53:54 -07:00
2017-12-19 11:33:55 -08:00
2018-01-16 12:16:54 -08:00
2018-08-15 15:08:23 -07:00
2018-10-19 13:34:02 +09:00
2018-09-17 13:53:52 -07:00
2018-10-30 15:43:39 +09:00
2018-10-30 15:43:39 +09:00
2018-09-17 13:53:54 -07:00
2018-03-15 12:01:08 -07:00
2018-08-20 15:31:40 -07:00
2018-10-19 13:34:02 +09:00
2018-09-17 13:53:57 -07:00
2018-10-19 13:34:02 +09:00
2018-06-01 15:06:37 +09:00
2018-08-15 15:08:25 -07:00
2018-09-27 11:53:39 -07:00
2018-09-17 13:53:54 -07:00
2018-10-19 13:34:02 +09:00
2018-08-02 15:30:39 -07:00
2018-08-15 11:52:09 -07:00
2018-05-30 21:51:28 +09:00
2018-10-19 13:34:02 +09:00
2018-08-15 15:08:25 -07:00
2018-08-20 12:41:32 -07:00
2018-07-18 12:20:28 -07:00
2018-10-19 13:34:02 +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.

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%