Derrick Stolee 4611884ea8 sequencer: notify user of --update-refs activity
When the user runs 'git rebase -i --update-refs', the end message still
says only

  Successfully rebased and updated <HEAD-ref>.

Update the sequencer to collect the successful (and unsuccessful) ref
updates due to the --update-refs option, so the end message now says

  Successfully rebased and updated <HEAD-ref>.
  Updated the following refs with --update-refs:
	refs/heads/first
	refs/heads/third
  Failed to update the following refs with --update-refs:
	refs/heads/second

To test this output, we need to be very careful to format the expected
error to drop the leading tab characters. Also, we need to be aware that
the verbose output from 'git rebase' is writing progress lines which
don't use traditional newlines but clear the line after every progress
item is complete. When opening the error file in an editor, these lines
are visible, but when looking at the diff in a terminal those lines
disappear because of the characters that delete the previous characters.
Use 'sed' to clear those progress lines and clear the tabs so we can get
an exact match on our expected output.

Reported-by: Elijah Newren <newren@gmail.com>
Signed-off-by: Derrick Stolee <derrickstolee@github.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2022-07-19 12:49:04 -07:00
2021-03-13 16:00:09 -08:00
2022-03-29 12:22:02 -07:00
2021-05-07 12:47:41 +09:00
2022-06-03 14:30:37 -07:00
2020-08-10 10:23:57 -07:00
2022-01-07 15:19:34 -08:00
2022-06-03 14:30:37 -07:00
2021-03-13 16:00:09 -08:00
2022-06-03 14:30:34 -07:00
2022-05-10 17:41:10 -07:00
2022-06-10 15:04:13 -07:00
2020-07-06 22:09:13 -07:00
2022-06-10 15:04:13 -07:00
2021-03-13 16:00:09 -08:00
2022-04-20 16:17:35 -07:00
2020-07-30 19:18:06 -07:00
2020-07-28 15:02:17 -07:00
2022-06-03 14:30:34 -07:00
2022-03-28 10:25:52 -07:00
2021-09-23 13:44:48 -07:00
2022-06-27 09:17:55 -07:00
2021-03-13 16:00:09 -08:00
2022-06-13 15:53:41 -07:00
2022-05-16 15:02:09 -07:00
2022-04-06 15:21:59 -07:00
2022-05-02 09:50:37 -07:00
2021-03-13 16:00:09 -08:00
2021-03-13 16:00:09 -08:00
2022-05-02 09:50:37 -07:00
2022-01-27 12:07:53 -08:00
2021-03-13 16:00:09 -08:00
2022-06-10 15:04:13 -07:00
2022-06-03 14:30:37 -07:00
2022-06-03 14:30:37 -07:00
2021-03-13 16:00:09 -08:00
2022-06-03 14:30:34 -07:00
2022-06-10 15:04:13 -07:00
2021-08-24 15:32:37 -07:00
2020-10-27 15:09:50 -07:00
2022-06-08 14:27:53 -07:00
2022-04-04 10:56:23 -07:00
2021-10-25 16:06:58 -07:00
2022-04-06 09:42:12 -07:00
2022-06-10 15:04:13 -07:00
2022-06-10 15:04:13 -07:00
2022-04-20 16:17:33 -07:00
2022-04-20 16:17:33 -07:00
2022-06-10 15:04:13 -07:00
2022-03-23 14:09:29 -07:00
2021-05-04 11:52:02 +09:00
2021-05-04 11:52:02 +09:00
2022-05-02 09:50:37 -07:00
2022-06-10 15:04:13 -07:00

Build status

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-<commandname>.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 and Documentation/CodingGuidelines).

Those wishing to help with error message, usage and informational message string translations (localization l10) should see po/README.md (a po file is a Portable Object file that holds the translations).

To subscribe to the list, send an email with just "subscribe git" in the body to majordomo@vger.kernel.org (not the Git list). The mailing list archives are available at https://lore.kernel.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 614 MiB
Languages
C 50.5%
Shell 38.7%
Perl 4.5%
Tcl 3.2%
Python 0.8%
Other 2.1%