git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "W. Trevor King" <wking@tremily.us>
To: Git <git@vger.kernel.org>
Cc: Junio C Hamano <gitster@pobox.com>,
	David Aguilar <davvid@gmail.com>,
	"W. Trevor King" <wking@tremily.us>
Subject: [PATCH v2 0/4] Update linux-2.6.git location and related examples
Date: Sat, 22 Jun 2013 10:46:23 -0400	[thread overview]
Message-ID: <cover.1371911897.git.wking@tremily.us> (raw)
In-Reply-To: <7vppvhye6s.fsf@alter.siamese.dyndns.org>

From: "W. Trevor King" <wking@tremily.us>

David and Junio mentioned that I'd missed a few 2.6 references in my
initial pass.  Here's a second attempt that does some deeper reworking
of the effected sections.  Each deeper rewrite gets its own patch and
motivation, with the final patch making all the superficial changes
that were not fixed in the earlier patches.

I've dropped the download size update (2/2 in v1), which Junio has
queued separately.  I also rebased the series on maint-1.8.2, since
that's where the size update landed.  I only touch low-churn areas
though, so this series should apply to any recent branch.

W. Trevor King (4):
  doc/clone: Remove the '--bare -l -s' example
  doc/clone: Pick more compelling paths for the --reference example
  Documentation: Update the NFS remote examples to use the staging repo
  Documentation: Update 'linux-2.6.git' -> 'linux.git'

 Documentation/git-clone.txt          | 19 ++++++-------------
 Documentation/git-fast-export.txt    |  2 +-
 Documentation/git-remote.txt         | 25 ++++++++++++++++---------
 Documentation/technical/racy-git.txt |  6 +++---
 Documentation/user-manual.txt        | 34 ++++++++++++++++++++--------------
 t/perf/README                        |  2 +-
 6 files changed, 47 insertions(+), 41 deletions(-)

-- 
1.8.3

  reply	other threads:[~2013-06-22 14:46 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-19  1:55 [PATCH 0/2] Update linux-2.6.git location and repo size W. Trevor King
2013-06-19  1:55 ` [PATCH 1/2] Documentation: Update 'linux-2.6.git' -> 'linux.git' W. Trevor King
2013-06-19  5:05   ` David Aguilar
2013-06-19 11:48     ` W. Trevor King
2013-06-19 19:47       ` W. Trevor King
2013-06-19 21:37         ` Junio C Hamano
2013-06-22 14:46           ` W. Trevor King [this message]
2013-06-22 14:46             ` [PATCH v2 1/4] doc/clone: Remove the '--bare -l -s' example W. Trevor King
2013-06-22 14:46             ` [PATCH v2 2/4] doc/clone: Pick more compelling paths for the --reference example W. Trevor King
2013-06-22 14:46             ` [PATCH v2 3/4] Documentation: Update the NFS remote examples to use the staging repo W. Trevor King
2013-06-22 14:46             ` [PATCH v2 4/4] Documentation: Update 'linux-2.6.git' -> 'linux.git' W. Trevor King
2013-06-30  1:05             ` [PATCH v2 0/4] Update linux-2.6.git location and related examples W. Trevor King
2013-06-30  1:44               ` Junio C Hamano
2013-06-30 10:48                 ` W. Trevor King
2013-06-19 17:07   ` [PATCH 1/2] Documentation: Update 'linux-2.6.git' -> 'linux.git' Junio C Hamano
2013-06-19  1:55 ` [PATCH 2/2] user-manual: Update download size for Git and the kernel W. Trevor King
2013-06-19 17:07   ` Junio C Hamano
2013-06-22 12:40   ` W. Trevor King

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=cover.1371911897.git.wking@tremily.us \
    --to=wking@tremily.us \
    --cc=davvid@gmail.com \
    --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.
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).