From: Junio C Hamano <gitster@pobox•com>
To: "Stephen P. Smith" <ischis2@cox•net>
Cc: Git List <git@vger•kernel.org>
Subject: Re: [PATCH V2] user-manual: add addition gitweb information
Date: Wed, 30 Dec 2015 15:29:09 -0800 [thread overview]
Message-ID: <xmqq7fjvcy7u.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <1451517920-30703-1-git-send-email-ischis2@cox.net> (Stephen P. Smith's message of "Wed, 30 Dec 2015 16:25:20 -0700")
"Stephen P. Smith" <ischis2@cox•net> writes:
> The gitweb cgi script provides users an easy way to browse your
> -project's files and history without having to install Git; see the file
> -gitweb/INSTALL in the Git source tree for instructions on setting it up.
> +project's revisions, file contents and logs without having to install
> +Git. Features like RSS/Atom feeds and blame/annotation details may
Thanks. Was there a reason to rewrite "files and history" into
"revisions, file contents and logs"? The words "revisions" and
"logs" both refer to the same thing and "history" is a good word for
it already, so I am puzzled. No strong objection, though...
> +optionally be enabled.
> +
> +The linkgit:git-instaweb[1] command provides a simple way to start
> +browsing the repository using gitweb. The default server when using
> +instaweb is lighttpd.
> +
> +See the file gitweb/INSTALL in the Git source tree and
> +linkgit:gitweb[1] for instructions on details setting up a permament
> +installation with a CGI or Perl capable server.
>
> [[sharing-development-examples]]
> Examples
> @@ -4651,8 +4660,6 @@ documentation.
> Add a section on working with other version control systems, including
> CVS, Subversion, and just imports of series of release tarballs.
>
> -More details on gitweb?
> -
> Write a chapter on using plumbing and writing scripts.
>
> Alternates, clone -reference, etc.
next prev parent reply other threads:[~2015-12-30 23:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-30 21:26 [PATCH] user-manual: add addition gitweb information Stephen P. Smith
2015-12-30 22:19 ` Junio C Hamano
2015-12-30 23:25 ` [PATCH V2] " Stephen P. Smith
2015-12-30 23:29 ` Junio C Hamano [this message]
2015-12-31 0:13 ` Stephen & Linda Smith
2015-12-31 0:23 ` Stephen & Linda Smith
2015-12-31 0:44 ` 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=xmqq7fjvcy7u.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=ischis2@cox$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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