Git development
 help / color / mirror / Atom feed
From: Michael Haggerty <mhagger@alum.mit.edu>
To: "Junio C Hamano" <gitster@pobox.com>,
	"Eric Sunshine" <sunshine@sunshineco.com>,
	"Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
Cc: git@vger.kernel.org, Michael Haggerty <mhagger@alum.mit.edu>
Subject: [PATCH 0/6] Various tweaks to 'worktree'-related manpages
Date: Sat, 18 Jul 2015 19:10:52 -0700	[thread overview]
Message-ID: <cover.1437271363.git.mhagger@alum.mit.edu> (raw)

I haven't been following the discussion of this feature on the mailing
list, so I apologize if these changes overlap with any in-flight
patches, and these changes should definitely be checked over by
somebody more familiar with the feature. These patches mostly fix what
seem like inconsistencies in the documentation. The last patch
contains some wordsmithing. Feel free to squash them together if you
prefer.

This patch series is also available from my GitHub account [1] as
branch "worktree-docs".

[1] https://github.com/mhagger/git

Michael Haggerty (6):
  worktree: consistently use term "linked working tree" in manpages
  worktree: remove references to "git checkout --to" from the manpage
  worktree: fix incorrect references to file "locked"
  worktree: the "locked" mechanism is already implemented
  config.txt: refer to "git worktree prune", not "prune --worktree"
  worktree: wordsmith worktree-related manpages

 Documentation/config.txt               | 10 +++++-----
 Documentation/git-worktree.txt         | 20 +++++++++-----------
 Documentation/gitrepository-layout.txt | 22 +++++++++++-----------
 3 files changed, 25 insertions(+), 27 deletions(-)

-- 
2.1.4

             reply	other threads:[~2015-07-19  2:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-19  2:10 Michael Haggerty [this message]
2015-07-19  2:10 ` [PATCH 1/6] worktree: consistently use term "linked working tree" in manpages Michael Haggerty
2015-07-19  2:54   ` Eric Sunshine
2015-07-19  2:10 ` [PATCH 2/6] worktree: remove references to "git checkout --to" from the manpage Michael Haggerty
2015-07-19  2:56   ` Eric Sunshine
2015-07-19  2:10 ` [PATCH 3/6] worktree: fix incorrect references to file "locked" Michael Haggerty
2015-07-19  3:04   ` Eric Sunshine
2015-07-19  2:10 ` [PATCH 4/6] worktree: the "locked" mechanism is already implemented Michael Haggerty
2015-07-19  3:06   ` Eric Sunshine
2015-07-19  2:10 ` [PATCH 5/6] config.txt: refer to "git worktree prune", not "prune --worktree" Michael Haggerty
2015-07-19  3:08   ` Eric Sunshine
2015-07-19  2:10 ` [PATCH 6/6] worktree: wordsmith worktree-related manpages Michael Haggerty
2015-07-19  3:21   ` Eric Sunshine
2015-07-19  2:50 ` [PATCH 0/6] Various tweaks to 'worktree'-related manpages Eric Sunshine

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=cover.1437271363.git.mhagger@alum.mit.edu \
    --to=mhagger@alum.mit.edu \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox