user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: "Štěpán Němec" <stepnem@smrk.net>
To: meta@public-inbox.org
Subject: [PATCH 1/2] doc: -cindex: correct and unify -g GIT_DIR usage string and man page
Date: Wed, 29 Nov 2023 13:02:51 +0100	[thread overview]
Message-ID: <20231129120252.1135398-1-stepnem@smrk.net> (raw)

Fixes: c76a20d75200 ("cindex: require `-g GIT_DIR' or `-r PROJECT_ROOT'")
---
 Documentation/public-inbox-cindex.pod | 2 +-
 script/public-inbox-cindex            | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/Documentation/public-inbox-cindex.pod b/Documentation/public-inbox-cindex.pod
index 0c9c4bdbff03..02c2d80f7ae5 100644
--- a/Documentation/public-inbox-cindex.pod
+++ b/Documentation/public-inbox-cindex.pod
@@ -4,7 +4,7 @@ public-inbox-cindex - create and update search for code repositories
 
 =head1 SYNOPSIS
 
-public-inbox-cindex [OPTIONS] -g GIT_DIR [-g GIT_DIR]
+public-inbox-cindex [OPTIONS] -g GIT_DIR [-g GIT_DIR]...
 
 public-inbox-cindex [OPTIONS] --update
 
diff --git a/script/public-inbox-cindex b/script/public-inbox-cindex
index a015d7a4f067..d61d0244833f 100755
--- a/script/public-inbox-cindex
+++ b/script/public-inbox-cindex
@@ -4,7 +4,7 @@
 use v5.12;
 use Getopt::Long qw(:config gnu_getopt no_ignore_case auto_abbrev);
 my $help = <<EOF; # the following should fit w/o scrolling in 80x24 term:
-usage: public-inbox-cindex [options] -g GIT_DIR...
+usage: public-inbox-cindex [options] -g GIT_DIR [-g GIT_DIR]...
 usage: public-inbox-cindex [options] --project-list=FILE -r PROJECT_ROOT
 
   Create and update search indices for code repos

base-commit: 59e3e12f23994538383f54f44e92e8a0d63070b2
-- 
2.43.0


             reply	other threads:[~2023-11-29 12:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-29 12:02 Štěpán Němec [this message]
2023-11-29 12:02 ` [PATCH 2/2] doc: fix a few typos and wording issues Štěpán Němec
2023-11-29 21:58   ` 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=20231129120252.1135398-1-stepnem@smrk.net \
    --to=stepnem@smrk.net \
    --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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/public-inbox.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).