# [PATCH] minor diff between gitweb docs and actual template for $GIT/description

3 messages from 2013-01-11 to 2013-01-11. Participants: Tim Chase, Jonathan Nieder.
Thread: https://gitlist.dev/t/32584

## Tim Chase, 2013-01-11 00:33

Subject: [PATCH] minor diff between gitweb docs and actual template for $GIT/description
Message-ID: <50EF5DC8.1000500@tim.thechases.com>
URL: https://gitlist.dev/e/50EF5DC8.1000500%40tim.thechases.com

```
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.

-tkc
(not subscribed to the actual git ML, just git-users@googlegroups.com)




diff --git a/Documentation/gitweb.txt b/Documentation/gitweb.txt
index 168e8bf..7c4cb69 100644
--- 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


diff --git a/templates/this--description b/templates/this--description
index 498b267..c6f25e8 100644
--- a/templates/this--description
+++ b/templates/this--description
@@ -1 +1 @@
-Unnamed repository; edit this file 'description' to name the repository.
+Unnamed repository; edit this file to name it for gitweb.

```

## Jonathan Nieder, 2013-01-11 02:22

Subject: Re: [PATCH] minor diff between gitweb docs and actual template for $GIT/description
Message-ID: <20130111022200.GH30784@google.com>
URL: https://gitlist.dev/e/20130111022200.GH30784%40google.com
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

```

## Tim Chase, 2013-01-11 04:25

Subject: Re: [PATCH] minor diff between gitweb docs and actual template for $GIT/description
Message-ID: <50EF944A.2040403@tim.thechases.com>
URL: https://gitlist.dev/e/50EF944A.2040403%40tim.thechases.com
In-Reply-To: <20130111022200.GH30784@google.com>

```
On 01/10/13 20:22, Jonathan Nieder wrote:
> (+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.)

Hahahahah...a one liner doc-fix copy/pasting code from one place in 
the codebase to another?  If you need it, you've got it:

   For my one line diff:
   Signed-off-by: Tim Chase <git@tim.thechases.com>

Otherwise, consider my contribution CC0 or public domain or whatever 
suits you best.  Or take my patch as a bug report and "make" the fix 
yourself. :-)

The patches should have been based off the master branch of 
github.com/git/git, FWIW.

-tkc
@gumnos

```
