Bug 753159 - Bad instances of '<file>' in messages in examples in '3.3. Git' chapter
Summary: Bad instances of '<file>' in messages in examples in '3.3. Git' chapter
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: doc-Developer_Guide
Version: 6.2
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: rc
: ---
Assignee: Jacquelynn East
QA Contact: ecs-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-11 13:47 UTC by Petr Muller
Modified: 2016-09-20 02:08 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-07 02:17:06 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Petr Muller 2011-11-11 13:47:46 UTC
Description of problem:

The chapter 3.3. Git contains lot of examples of git command output. A lot of messages containg a snippet like this:

"Foobar <file> was foobared"
        ^^^^^^

However, in some output examples, the '<file>' part is borked in various ways:

3.3.4. Untracked files, snippet 1
#	(use "git add <file<..." to include in what will be committed)
                      ^^^^^^
3.3.6. Modified Status, snippet 2 and 3
#	(use "git reset HEAD >file<..." to unstage)
                             ^^^^^^


Note You need to log in before you can comment on or make changes to this bug.