From: "Михаил Павлович Сидоренко" <motherlode.muwa@gmail.com>
To: git@vger.kernel.org
Subject: git show submodule
Date: Wed, 30 Dec 2020 11:29:32 +0400 [thread overview]
Message-ID: <4ddc481f-7d03-e225-13a0-d5fd33456c43@gmail.com> (raw)
In-Reply-To: <ab49430e-5a9f-5910-e048-7f07dca8f898@gmail.com>
Hello!
git show dose not work with file-submodule. Try this series of commands:
cd /tmp/
git clone https://github.com/abdes/submodule-docker-dev-workflow.git
cd submodule-docker-dev-workflow
git show ee83dd336f27315d14a7ad6ad934897a61e49623:LICENSE | head -n 1 #
good
git show ee83dd336f27315d14a7ad6ad934897a61e49623:server # bad
My output:
$ cd /tmp/
$ git clone https://github.com/abdes/submodule-docker-dev-workflow.git
Клонирование в «submodule-docker-dev-workflow»…
remote: Enumerating objects: 110, done.
remote: Total 110 (delta 0), reused 0 (delta 0), pack-reused 110
Получение объектов: 100% (110/110), 24.76 KiB | 313.00 KiB/s, готово.
Определение изменений: 100% (56/56), готово.
$ cd submodule-docker-dev-workflow
$ git show ee83dd336f27315d14a7ad6ad934897a61e49623:LICENSE | head -n 1
# good
The MIT License (MIT)
$ git show ee83dd336f27315d14a7ad6ad934897a61e49623:server # bad
fatal: bad object ee83dd336f27315d14a7ad6ad934897a61e49623:server
It would be convenient for me so that I could see the revision of the
submodule through git show. Without using the git submodule status command.
Happy New Year,
Mikhail Pavlovich Sidorenko.
next parent reply other threads:[~2020-12-30 7:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ab49430e-5a9f-5910-e048-7f07dca8f898@gmail.com>
2020-12-30 7:29 ` Михаил Павлович Сидоренко [this message]
2020-12-30 16:13 ` git show submodule Philippe Blain
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=4ddc481f-7d03-e225-13a0-d5fd33456c43@gmail.com \
--to=motherlode.muwa@gmail.com \
--cc=git@vger.kernel.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 NNTP newsgroup(s).