From: Junio C Hamano <gitster@pobox.com>
To: Jamey Sharp <jamey@minilop.net>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Shawn O. Pearce" <spearce@spearce.org>,
"Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
"Jeff King" <peff@peff.net>, "Jakub Narebski" <jnareb@gmail.com>,
git@vger.kernel.org, "Josh Triplett" <josh@joshtriplett.org>
Subject: Re* [PATCH 4/4] Add documentation for ref namespaces
Date: Thu, 15 Sep 2011 17:22:29 -0700 [thread overview]
Message-ID: <7vaaa5pc8q.fsf_-_@alter.siamese.dyndns.org> (raw)
In-Reply-To: <CACBZZX4bow8vwrwSL5uRJQtAgeg10_K+5ss8u-HvCHOn3+0Tuw@mail.gmail.com> ("Ævar Arnfjörð Bjarmason"'s message of "Tue, 23 Aug 2011 12:38:04 +0200")
Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
> On Tue, Jun 7, 2011 at 20:21, Jamey Sharp <jamey@minilop.net> wrote:
>
>> Document the namespace mechanism in a new gitnamespaces(7) page.
>> Reference it from receive-pack and upload-pack.
>
> This breaks the build on older asciidoc versions, the fix is to do
> what I did in f5008f56d5aba06598e1c6272f4f55b4ee4bb016.
Earlier I sent out a tongue-in-cheek "like this" that had a completely
bogus SYNOPSIS section that is unusable in a released version of Git,
hoping that somebody who _care_ more about the feature that the page
describes would give us a better wording, but unfortunately it never
happened.
So here is a more realistic replacement, so that we won't have to suffer
by complaints from people with older AsciiDoc saying "the release does not
build". If we were to include this in 1.7.7 final, we now need to make
sure we won't to have to hear from people with newer AsciiDoc saying "why
do we have nonsense in SYNOPSIS section", so your help is needed here.
I explicitly avoided saying:
[verse]
export GIT_NAMESPACE=<namespace>
as nothing other than the selected transports seems to pay attention to
this environment variable.
-- >8 --
Subject: [PATCH] Documentation/gitnamespaces.txt: cater to older asciidoc
Older asciidoc (e.g. 8.2.5 on Centos 5.5) is unhappy if a manpage does not
have a SYNOPSIS section. Show a sample (and a possibly bogus) command line
of running two commands that pay attention to this environment variable
with a customized value.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
---
Documentation/gitnamespaces.txt | 7 +++++++
1 files changed, 7 insertions(+), 0 deletions(-)
diff --git a/Documentation/gitnamespaces.txt b/Documentation/gitnamespaces.txt
index ed8924e..c6713cf 100644
--- a/Documentation/gitnamespaces.txt
+++ b/Documentation/gitnamespaces.txt
@@ -5,6 +5,13 @@ NAME
----
gitnamespaces - Git namespaces
+SYNOPSIS
+--------
+[verse]
+GIT_NAMESPACE=<namespace> 'git upload-pack'
+GIT_NAMESPACE=<namespace> 'git receive-pack'
+
+
DESCRIPTION
-----------
--
1.7.7.rc1.3.g559357
next prev parent reply other threads:[~2011-09-16 0:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-06 6:29 What's cooking in git.git (Jun 2011, #01; Sun, 5) Junio C Hamano
2011-06-06 7:16 ` Johannes Sixt
2011-06-06 7:38 ` Erik Faye-Lund
2011-06-07 18:21 ` Jamey Sharp
2011-06-07 18:21 ` [PATCH 1/4] Fix prefix handling in ref iteration functions Jamey Sharp
2011-06-07 18:21 ` [PATCH 2/4] Add infrastructure for ref namespaces Jamey Sharp
2011-06-07 19:12 ` Bert Wesarg
2011-06-07 22:25 ` Josh Triplett
2011-06-07 18:21 ` [PATCH 3/4] Support ref namespaces for remote repositories via upload-pack and receive-pack Jamey Sharp
2011-06-07 18:21 ` [PATCH 4/4] Add documentation for ref namespaces Jamey Sharp
2011-08-23 10:38 ` Ævar Arnfjörð Bjarmason
2011-08-23 17:19 ` Junio C Hamano
2011-08-24 12:30 ` Ævar Arnfjörð Bjarmason
2011-09-16 0:22 ` Junio C Hamano [this message]
2011-09-16 3:40 ` Re* " Jamey Sharp
2011-09-16 16:20 ` Junio C Hamano
2011-06-07 18:59 ` What's cooking in git.git (Jun 2011, #01; Sun, 5) 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=7vaaa5pc8q.fsf_-_@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=jamey@minilop.net \
--cc=jnareb@gmail.com \
--cc=josh@joshtriplett.org \
--cc=peff@peff.net \
--cc=spearce@spearce.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).