git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavan Kumar Sunkara <pavan.sss1991@gmail.com>
To: git@vger.kernel.org
Cc: Pavan Kumar Sunkara <pavan.sss1991@gmail.com>
Subject: [PATCH] Documentation/Notes: Remove 'footnote:' warning
Date: Sun, 17 Jul 2011 04:00:20 +0530	[thread overview]
Message-ID: <1310855420-21183-1-git-send-email-pavan.sss1991@gmail.com> (raw)

Remove 'footnote:' from git-notes.txt which is responsible
for the warnings surfacing during the generation of git
documentation.
---
 Documentation/git-notes.txt |    9 +++++----
 1 files changed, 5 insertions(+), 4 deletions(-)

diff --git a/Documentation/git-notes.txt b/Documentation/git-notes.txt
index 6a187f2..2a18894 100644
--- a/Documentation/git-notes.txt
+++ b/Documentation/git-notes.txt
@@ -210,10 +210,11 @@ Commit notes are blobs containing extra information about an object
 are taken from notes refs.  A notes ref is usually a branch which
 contains "files" whose paths are the object names for the objects
 they describe, with some directory separators included for performance
-reasons footnote:[Permitted pathnames have the form
-'ab'`/`'cd'`/`'ef'`/`'...'`/`'abcdef...': a sequence of directory
-names of two hexadecimal digits each followed by a filename with the
-rest of the object ID.].
+reasons.
+
+Permitted pathnames have the form 'ab'`/`'cd'`/`'ef'`/`'...'`/`'abcdef...':
+a sequence of directory names of two hexadecimal digits each
+followed by a filename with the rest of the object ID.
 
 Every notes change creates a new commit at the specified notes ref.
 You can therefore inspect the history of the notes by invoking, e.g.,
-- 
1.7.6.485.gad3dc

             reply	other threads:[~2011-07-16 22:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-16 22:30 Pavan Kumar Sunkara [this message]
2011-07-17 13:11 ` [PATCH] Documentation/Notes: Remove 'footnote:' warning Drew Northup
     [not found]   ` <CAK9CXBUAX42gCuRLWUpuvK6SSZXv1Cn4YNoFAfjRhouzd+thcw@mail.gmail.com>
2011-07-17 13:46     ` Pavan Kumar Sunkara
2011-07-17 21:58   ` Jonathan Nieder
2011-07-18  5:42     ` Pavan Kumar Sunkara
2011-07-18  5:51       ` Jonathan Nieder
2011-07-18  6:07         ` Pavan Kumar Sunkara
2011-07-18  7:13           ` Jonathan Nieder
2011-07-18  9:01             ` Pavan Kumar Sunkara
2011-07-19 20:43               ` Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1310855420-21183-1-git-send-email-pavan.sss1991@gmail.com \
    --to=pavan.sss1991@gmail.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).