From: Junio C Hamano <gitster@pobox.com>
To: Taylor Blau <me@ttaylorr.com>
Cc: Eric Sunshine <sunshine@sunshineco.com>,
git@vger.kernel.org, Duy Nguyen <pclouds@gmail.com>
Subject: Re: [PATCH 0/4] git-worktree documentation cleanups
Date: Mon, 03 Aug 2020 10:14:44 -0700 [thread overview]
Message-ID: <xmqq3653wt17.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <20200803161102.GB50799@syl.lan> (Taylor Blau's message of "Mon, 3 Aug 2020 12:11:02 -0400")
Taylor Blau <me@ttaylorr.com> writes:
> Hi Eric,
>
> On Mon, Aug 03, 2020 at 01:36:08AM -0400, Eric Sunshine wrote:
>> This series fixes some problems I ran across in the git-worktree
>> documentation while working on another worktree-related topic. Since
>> these fixes are distinct from that topic, I'm submitting them
>> separately.
>>
>> Eric Sunshine (4):
>> git-worktree.txt: employ fixed-width typeface consistently
>> git-worktree.txt: consistently use term "working tree"
>> git-worktree.txt: fix minor grammatical issues
>> git-worktree.txt: make start of new sentence more obvious
>>
>> Documentation/git-worktree.txt | 96 +++++++++++++++++-----------------
>> 1 file changed, 48 insertions(+), 48 deletions(-)
>
> All looks good to me. Thanks.
>
> Reviewed-by: Taylor Blau <me@ttaylorr.com>
Yeah, they looked good to me, too. Thanks, both.
next prev parent reply other threads:[~2020-08-03 17:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-03 5:36 [PATCH 0/4] git-worktree documentation cleanups Eric Sunshine
2020-08-03 5:36 ` [PATCH 1/4] git-worktree.txt: employ fixed-width typeface consistently Eric Sunshine
2020-08-03 5:36 ` [PATCH 2/4] git-worktree.txt: consistently use term "working tree" Eric Sunshine
2020-08-03 5:36 ` [PATCH 3/4] git-worktree.txt: fix minor grammatical issues Eric Sunshine
2020-08-03 5:36 ` [PATCH 4/4] git-worktree.txt: make start of new sentence more obvious Eric Sunshine
2020-08-03 16:11 ` [PATCH 0/4] git-worktree documentation cleanups Taylor Blau
2020-08-03 17:14 ` Junio C Hamano [this message]
2020-08-03 17:57 ` Martin Ågren
2020-08-03 23:54 ` Eric Sunshine
2020-08-04 0:15 ` Junio C Hamano
2020-08-04 0:55 ` [PATCH v2 0/5] " Eric Sunshine
2020-08-04 0:55 ` [PATCH v2 1/5] git-worktree.txt: employ fixed-width typeface consistently Eric Sunshine
2020-08-04 0:55 ` [PATCH v2 2/5] git-worktree.txt: consistently use term "working tree" Eric Sunshine
2020-08-04 0:55 ` [PATCH v2 3/5] git-worktree.txt: fix minor grammatical issues Eric Sunshine
2020-08-04 0:55 ` [PATCH v2 4/5] git-worktree.txt: make start of new sentence more obvious Eric Sunshine
2020-08-04 0:55 ` [PATCH v2 5/5] git-wortkree.txt: link to man pages when citing other Git commands Eric Sunshine
2020-08-04 1:10 ` [PATCH v2 0/5] git-worktree documentation cleanups Taylor Blau
2020-08-04 4:28 ` Martin Ågren
2020-08-04 4:44 ` Eric Sunshine
2020-08-04 5:23 ` Martin Ågren
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq3653wt17.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=me@ttaylorr.com \
--cc=pclouds@gmail.com \
--cc=sunshine@sunshineco.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).