From: Stefan Beller <sbeller@google.com>
To: Per Cederqvist <cederp@opera.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: "git submodule deinit -f ." no longer works when there are no submodules
Date: Tue, 22 Mar 2016 10:13:27 -0700 [thread overview]
Message-ID: <CAGZ79kYVLaZg6APM0rfQkZjQRrh7bKBiZb39boucTAqH47eR1A@mail.gmail.com> (raw)
In-Reply-To: <CAP=KgsRjJ9JNKe07GRpcNP3eQK8+zYDvUpXkp-9WgiQUq0bgcA@mail.gmail.com>
On Tue, Mar 22, 2016 at 2:25 AM, Per Cederqvist <cederp@opera.com> wrote:
> It used to be possible to run
>
> git submodule deinit -f .
>
> to remove any submodules, no matter how many submodules you had. That
> is no longer possible in projects that don't have any submodules at
> all. The command will fail with:
>
> error: pathspec '.' did not match any file(s) known to git.
>
> But if I run "git submodule deinit" (without the ".") git tells me:
>
> Use '.' if you really want to deinitialize all submodules
>
> This is a regression introduced in Git 2.7.0 (and v2.7.0-rv0). "git
> bisect" points to this commit:
>
> commit 74703a1e4dfc5affcb8944e78b53f0817b492246 (refs/bisect/bad)
> Author: Stefan Beller <sbeller@google.com>
> Date: 2015-09-02 14:42:24 -0700
>
> submodule: rewrite `module_list` shell function in C
>
> One could argue that it makes no sense to run "git submodule deinit -f
> ." in a repository with no submodules. I've written a continuous
> integration system for a project where some branches have submodules
> and other don't, and I found it convenient to don't have to treat
> those branches differently.
>
> The following shellscript demonstrates the issue. It passes on git
> version before 2.7.0, and fails on later versions.
Thanks for the bug report, I'll fix it.
Stefan
>
> --- cut here ---
> #!/bin/sh
> #
> # This script demonstrates the "git submodule deinit ." bug.
> #
>
> if ! mkdir subdeinit
> then
> echo 'Covardly refusing to alter the "subdeinit" directory.' >&2
> echo 'Please remove it, or run this script inside an empty directory.' >&2
> exit 1
> fi
>
> cd subdeinit
> mkdir repo
> cd repo
> git init
> echo test > test
> git add test
> git commit -m"Create an initial commit."
> if git submodule deinit -f .
> then
> echo PASS: git submodule deinit -f . is allowed.
> exit 0
> else
> echo FAIL: git submodule deinit -f . is not allowed.
> exit 1
> fi
> --- cut here ---
>
> Yours,
> /ceder
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2016-03-22 17:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-22 9:25 "git submodule deinit -f ." no longer works when there are no submodules Per Cederqvist
2016-03-22 17:13 ` Stefan Beller [this message]
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=CAGZ79kYVLaZg6APM0rfQkZjQRrh7bKBiZb39boucTAqH47eR1A@mail.gmail.com \
--to=sbeller@google.com \
--cc=cederp@opera.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).