From: "Shao-Ce SUN via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Shao-Ce SUN <sunshaoce@iscas.ac.cn>, Shao-Ce SUN <sunshaoce@iscas.ac.cn>
Subject: [PATCH] Fix wrong info in `INSTALL`
Date: Tue, 24 May 2022 20:43:18 +0000 [thread overview]
Message-ID: <pull.1241.git.1653424998869.gitgitgadget@gmail.com> (raw)
From: Shao-Ce SUN <sunshaoce@iscas.ac.cn>
The user prompt should be `$` instead of `#`.
Signed-off-by: Shao-Ce SUN <sunshaoce@iscas.ac.cn>
---
Fix wrong info in INSTALL
The user prompt should be $ instead of #.
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-1241%2Fsunshaoce%2Finstall-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-1241/sunshaoce/install-v1
Pull-Request: https://github.com/gitgitgadget/git/pull/1241
INSTALL | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/INSTALL b/INSTALL
index 4140a3f5c8b..7bb3f48311d 100644
--- a/INSTALL
+++ b/INSTALL
@@ -5,8 +5,8 @@ Normally you can just do "make" followed by "make install", and that
will install the git programs in your own ~/bin/ directory. If you want
to do a global install, you can do
- $ make prefix=/usr all doc info ;# as yourself
- # make prefix=/usr install install-doc install-html install-info ;# as root
+ $ make prefix=/usr all doc info ; $ as yourself
+ # make prefix=/usr install install-doc install-html install-info ; # as root
(or prefix=/usr/local, of course). Just like any program suite
that uses $prefix, the built results have some paths encoded,
@@ -20,10 +20,10 @@ config.mak file.
Alternatively you can use autoconf generated ./configure script to
set up install paths (via config.mak.autogen), so you can write instead
- $ make configure ;# as yourself
- $ ./configure --prefix=/usr ;# as yourself
- $ make all doc ;# as yourself
- # make install install-doc install-html;# as root
+ $ make configure ; $ as yourself
+ $ ./configure --prefix=/usr ; $ as yourself
+ $ make all doc ; $ as yourself
+ # make install install-doc install-html; # as root
If you're willing to trade off (much) longer build time for a later
faster git you can also do a profile feedback build with
base-commit: 7a3eb286977746bc09a5de7682df0e5a7085e17c
--
gitgitgadget
next reply other threads:[~2022-05-24 20:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-24 20:43 Shao-Ce SUN via GitGitGadget [this message]
2022-05-24 21:39 ` [PATCH] Fix wrong info in `INSTALL` Ævar Arnfjörð Bjarmason
2022-05-24 22:03 ` Philippe Blain
2022-05-24 22:21 ` Junio C Hamano
2022-05-25 5:29 ` Christian Couder
2022-05-25 16:05 ` Junio C Hamano
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=pull.1241.git.1653424998869.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=git@vger.kernel.org \
--cc=sunshaoce@iscas.ac.cn \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.