Torstein Hegge 6b364d48f2 branch: fix --verbose output column alignment
Commit f2e0873 (branch: report invalid tracking branch as gone) removed
an early return from fill_tracking_info() in the path taken when 'git
branch -v' lists a branch in sync with its upstream. This resulted in an
unconditionally added space in front of the subject line:

    $ git branch -v
    * master f5eb3da  commit pushed to upstream
      topic  f935eb6 unpublished topic

Instead, only add the trailing space if a decoration have been added.

To catch this kind of whitespace breakage in the tests, be a bit less
smart when filtering the output through sed.

Signed-off-by: Torstein Hegge <hegge@resisty.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2013-11-18 11:24:08 -08:00
2013-08-08 14:03:21 -07:00
2013-05-09 13:32:54 -07:00
2013-07-22 11:24:14 -07:00
2013-08-13 10:49:33 -07:00
2012-10-25 06:42:02 -04:00
2012-10-29 03:08:30 -04:00
2013-08-01 12:01:01 -07:00
2013-06-10 10:55:42 -07:00
2013-07-29 12:32:25 -07:00
2013-08-05 10:11:04 -07:00
2013-07-25 16:06:23 -07:00
2013-07-22 11:24:09 -07:00
2013-07-22 16:06:49 -07:00
2013-07-22 16:06:49 -07:00
2013-07-24 19:20:59 -07:00
2013-05-29 14:23:04 -07:00
2013-07-24 19:23:01 -07:00
2013-02-17 15:25:52 -08:00
2013-07-19 09:26:15 -07:00
2012-11-28 13:52:54 -08:00
2013-07-29 12:32:25 -07:00
2013-07-29 12:32:25 -07:00
2013-08-13 11:10:18 -07:00
2013-07-22 11:24:14 -07:00
2012-04-06 10:15:11 -07:00
2013-05-08 15:31:54 -07:00
2013-04-19 13:31:08 -07:00
2013-04-11 17:39:05 -07:00
2013-07-22 16:06:49 -07:00
2013-07-15 10:28:40 -07:00
2013-07-15 08:23:39 -07:00
2013-04-03 09:18:01 -07:00
2013-07-29 12:32:25 -07:00
2012-10-29 03:08:30 -04:00
2013-08-09 15:49:55 -07:00
2012-08-03 12:11:07 -07:00
2013-07-29 12:32:25 -07:00
2013-02-05 16:13:32 -08:00
2013-07-19 11:15:17 -07:00
2013-07-09 12:34:16 -07:00
2013-07-22 11:24:11 -07:00
2013-07-22 11:23:35 -07:00
2013-06-20 16:02:18 -07:00
2013-07-29 12:32:25 -07:00
2013-07-22 11:23:13 -07:00

////////////////////////////////////////////////////////////////

	Git - the stupid content tracker

////////////////////////////////////////////////////////////////

"git" can mean anything, 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

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.

See Documentation/gittutorial.txt to get started, then see
Documentation/everyday.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).

Many Git online resources are accessible from http://git-scm.com/
including full documentation and Git related tools.

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 http://news.gmane.org/gmane.comp.version-control.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.
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%