From: Jonathan Nieder <jrnieder@gmail.com>
To: Tim Chase <git@tim.thechases.com>
Cc: git@vger.kernel.org, Jakub Narebski <jnareb@gmail.com>
Subject: Re: [PATCH] minor diff between gitweb docs and actual template for $GIT/description
Date: Thu, 10 Jan 2013 18:22:01 -0800 [thread overview]
Message-ID: <20130111022200.GH30784@google.com> (raw)
In-Reply-To: <50EF5DC8.1000500@tim.thechases.com>
(+cc: Jakub, who maintains gitweb)
Hi Tim,
Tim Chase wrote:
> The documentation for gitweb gives one description of the default
> content for the $GIT/description, the description template has other
> text. One of these two patches should be applied to bring them into
> order (applying both would just reverse the problem). Or, both
> could be changed to the same new text.
May we have your sign-off? (See Documentation/SubmittingPatches for
what this means.)
> --- a/Documentation/gitweb.txt
> +++ b/Documentation/gitweb.txt
> @@ -227,7 +227,7 @@ description (or `gitweb.description`)::
> repository). Plain text file; HTML will be escaped. By default set to
> +
> -------------------------------------------------------------------------------
> -Unnamed repository; edit this file to name it for gitweb.
> +Unnamed repository; edit this file 'description' to name the repository.
> -------------------------------------------------------------------------------
> +
> from the template during repository creation, usually installed in
Looks sane to me. Thanks for noticing.
Regards,
Jonathan
next prev parent reply other threads:[~2013-01-11 2:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-11 0:33 [PATCH] minor diff between gitweb docs and actual template for $GIT/description Tim Chase
2013-01-11 2:22 ` Jonathan Nieder [this message]
2013-01-11 4:25 ` Tim Chase
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=20130111022200.GH30784@google.com \
--to=jrnieder@gmail.com \
--cc=git@tim.thechases.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.