From: Stephen & Linda Smith <ischis2@cox.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: [PATCH V2] user-manual: add addition gitweb information
Date: Wed, 30 Dec 2015 17:13:04 -0700 [thread overview]
Message-ID: <2046573.P07fx7UGVP@thunderbird> (raw)
In-Reply-To: 1451517920-30703-1-git-send-email-ischis2@cox.net
On Wednesday, December 30, 2015 03:29:09 PM Junio C Hamano wrote:
> "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...
>
"revisions, file contents and logs was in the second sentence of the first patch.
"files and history" was in the first sentence of the first patch.
When I was getting rid of the duplication I decided that "revisions, file contents and logs".
As a secondary reason that is the wording in gitweb.txt.
next prev parent reply other threads:[~2015-12-31 0:13 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
2015-12-31 0:13 ` Stephen & Linda Smith [this message]
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=2046573.P07fx7UGVP@thunderbird \
--to=ischis2@cox.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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 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).