From: Tim Janik <timj@gnu.org>
To: git@vger.kernel.org
Subject: fetch unshallow fails to honor dry-run
Date: Sun, 25 Oct 2015 10:16:00 +0100 [thread overview]
Message-ID: <562C9DD0.5040109@gnu.org> (raw)
Hey all,
git fetch --dry-run modifies the repository if --unshallow is passed:
$ git --version
git version 2.1.4
$ git fetch --dry-run --unshallow
remote: Counting objects: 30603, done.
remote: Compressing objects: 100% (6843/6843), done.
remote: Total 30603 (delta 24564), reused 29164 (delta 23386)
Receiving objects: 100% (30603/30603), 5.42 MiB | 0 bytes/s, done.
Resolving deltas: 100% (24564/24564), completed with 317 local objects.
remote: Counting objects: 7, done.
remote: Compressing objects: 100% (7/7), done.
remote: Total 7 (delta 0), reused 6 (delta 0)
Unpacking objects: 100% (7/7), done.
I actually tried --dry-run --unshallow in order to find a way to detect in a script if the current git repository is shallow or not.
Better suggestions to find this out are very welcome.
--
Yours sincerely,
Tim Janik
https://testbit.eu/timj/
Free software author and speaker.
next reply other threads:[~2015-10-25 9:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-25 9:16 Tim Janik [this message]
2015-11-09 19:24 ` fetch unshallow fails to honor dry-run Jeff King
2015-11-14 18:19 ` Duy Nguyen
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=562C9DD0.5040109@gnu.org \
--to=timj@gnu.org \
--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).