From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: Re: [PATCH 2/3] doc: update public-inbox-overview(7) for v2
Date: Thu, 17 Oct 2019 07:42:25 +0000 [thread overview]
Message-ID: <20191017074225.wko4qvh7hdis7bjv@dcvr> (raw)
In-Reply-To: <20191016111451.32255-3-e@80x24.org>
Eric Wong <e@80x24.org> wrote:
> diff --git a/Documentation/public-inbox-overview.pod b/Documentation/public-inbox-overview.pod
> index 46060d0c..782c2f8b 100644
> --- a/Documentation/public-inbox-overview.pod
> +++ b/Documentation/public-inbox-overview.pod
> + # for v2, in most cases, only the most recent epoch needs to be fetched:
> + git --git-dir=INBOX_DIR/git/EPOCH.git fetch
That was >80 columns and breaks "check-man"
(that target needs to run by default, at least on gmake)
diff --git a/Documentation/public-inbox-overview.pod b/Documentation/public-inbox-overview.pod
index 782c2f8..91d4a88 100644
--- a/Documentation/public-inbox-overview.pod
+++ b/Documentation/public-inbox-overview.pod
@@ -56,7 +56,7 @@ that inbox. The instructions are roughly:
# for v1 inboxes:
git --git-dir=INBOX_DIR fetch
- # for v2, in most cases, only the most recent epoch needs to be fetched:
+ # for v2 (in most cases, only the newest epoch needs to be fetched):
git --git-dir=INBOX_DIR/git/EPOCH.git fetch
# index new messages after fetching:
next prev parent reply other threads:[~2019-10-17 7:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-16 11:14 [PATCH 0/3] another round of doc updates Eric Wong
2019-10-16 11:14 ` [PATCH 1/3] doc: check-man: use COLUMNS env for width Eric Wong
2019-10-16 11:14 ` [PATCH 2/3] doc: update public-inbox-overview(7) for v2 Eric Wong
2019-10-17 7:42 ` Eric Wong [this message]
2019-10-16 11:14 ` [PATCH 3/3] doc: avoid [<directory>] arg for git-clone(1) Eric Wong
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: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191017074225.wko4qvh7hdis7bjv@dcvr \
--to=e@80x24.org \
--cc=meta@public-inbox.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).