empty string is not a valid pathspec
After reading Git - git-submodule Documentation, I decided to import two files from my previous project into the root directory of my new project, because I don't want to manually synchronize these two files.
However, an error occurs when I executed the following command:
$ git submodule add -b master -f --name latexci -- https://github.com/donizyo/LaTeX-Travis.git .
fatal: empty string is not a valid pathspec. please use . instead if you meant to match all paths
usage: git submodule--helper clone [--prefix=<path>] [--quiet] [--reference <repository>] [--name <name>] [--depth <depth>] --url <url> --path <path>
--prefix <path> alternative anchor for relative paths
--path <path> where the new submodule will be cloned to
--name <string> name of the new submodule
--url <string> url where to clone the submodule from
--reference <repo> reference repository
--dissociate use --reference only while cloning
--depth <string> depth for shallow clones
-q, --quiet Suppress output for cloning a submodule
--progress force cloning progress
I'm using Git Bash 2.19.1.windows.1 to execute git commands.
git git-bash
asked Nov 23 '18 at 4:12
KaiserKatze
7321621
add a comment |
After reading Git - git-submodule Documentation, I decided to import two files from my previous project into the root directory of my new project, because I don't want to manually synchronize these two files.
However, an error occurs when I executed the following command:
$ git submodule add -b master -f --name latexci -- https://github.com/donizyo/LaTeX-Travis.git .
fatal: empty string is not a valid pathspec. please use . instead if you meant to match all paths
usage: git submodule--helper clone [--prefix=<path>] [--quiet] [--reference <repository>] [--name <name>] [--depth <depth>] --url <url> --path <path>
--prefix <path> alternative anchor for relative paths
--path <path> where the new submodule will be cloned to
--name <string> name of the new submodule
--url <string> url where to clone the submodule from
--reference <repo> reference repository
--dissociate use --reference only while cloning
--depth <string> depth for shallow clones
-q, --quiet Suppress output for cloning a submodule
--progress force cloning progress
I'm using Git Bash 2.19.1.windows.1 to execute git commands.
git git-bash
asked Nov 23 '18 at 4:12
KaiserKatze
7321621
add a comment |
After reading Git - git-submodule Documentation, I decided to import two files from my previous project into the root directory of my new project, because I don't want to manually synchronize these two files.
However, an error occurs when I executed the following command:
$ git submodule add -b master -f --name latexci -- https://github.com/donizyo/LaTeX-Travis.git .
fatal: empty string is not a valid pathspec. please use . instead if you meant to match all paths
usage: git submodule--helper clone [--prefix=<path>] [--quiet] [--reference <repository>] [--name <name>] [--depth <depth>] --url <url> --path <path>
--prefix <path> alternative anchor for relative paths
--path <path> where the new submodule will be cloned to
--name <string> name of the new submodule
--url <string> url where to clone the submodule from
--reference <repo> reference repository
--dissociate use --reference only while cloning
--depth <string> depth for shallow clones
-q, --quiet Suppress output for cloning a submodule
--progress force cloning progress
I'm using Git Bash 2.19.1.windows.1 to execute git commands.
git git-bash
asked Nov 23 '18 at 4:12
KaiserKatze
7321621
After reading Git - git-submodule Documentation, I decided to import two files from my previous project into the root directory of my new project, because I don't want to manually synchronize these two files.
However, an error occurs when I executed the following command:
$ git submodule add -b master -f --name latexci -- https://github.com/donizyo/LaTeX-Travis.git .
fatal: empty string is not a valid pathspec. please use . instead if you meant to match all paths
usage: git submodule--helper clone [--prefix=<path>] [--quiet] [--reference <repository>] [--name <name>] [--depth <depth>] --url <url> --path <path>
--prefix <path> alternative anchor for relative paths
--path <path> where the new submodule will be cloned to
--name <string> name of the new submodule
--url <string> url where to clone the submodule from
--reference <repo> reference repository
--dissociate use --reference only while cloning
--depth <string> depth for shallow clones
-q, --quiet Suppress output for cloning a submodule
--progress force cloning progress
I'm using Git Bash 2.19.1.windows.1 to execute git commands.
git git-bash
git git-bash
asked Nov 23 '18 at 4:12
KaiserKatze
7321621
asked Nov 23 '18 at 4:12
KaiserKatze
7321621
asked Nov 23 '18 at 4:12
KaiserKatze
7321621
asked Nov 23 '18 at 4:12
KaiserKatze
7321621
asked Nov 23 '18 at 4:12
KaiserKatze
7321621
7321621
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
The path (.) should be a non-existent folder, like Latex-Travis.
Instead, here '.' is interpreted as an empty path (since it is refereing to your parent repo), and as illustrated in ruby-git/ruby-git issue 345:
This really was deprecated since Git 2.1.6:
An empty string as a pathspec element that means "everything" i.e. 'git add ""', is now illegal. We started this by first deprecating and warning a pathspec that has such an element in 2.11 (Nov 2016).
I am not aware of a submodule added directly within a parent repo folder: I always used to add as a parent repo subfolder.
answered Nov 23 '18 at 5:42
VonC
830k28926113157
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53440570%2fempty-string-is-not-a-valid-pathspec%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The path (.) should be a non-existent folder, like Latex-Travis.
Instead, here '.' is interpreted as an empty path (since it is refereing to your parent repo), and as illustrated in ruby-git/ruby-git issue 345:
This really was deprecated since Git 2.1.6:
An empty string as a pathspec element that means "everything" i.e. 'git add ""', is now illegal. We started this by first deprecating and warning a pathspec that has such an element in 2.11 (Nov 2016).
I am not aware of a submodule added directly within a parent repo folder: I always used to add as a parent repo subfolder.
answered Nov 23 '18 at 5:42
VonC
830k28926113157
add a comment |
The path (.) should be a non-existent folder, like Latex-Travis.
Instead, here '.' is interpreted as an empty path (since it is refereing to your parent repo), and as illustrated in ruby-git/ruby-git issue 345:
This really was deprecated since Git 2.1.6:
An empty string as a pathspec element that means "everything" i.e. 'git add ""', is now illegal. We started this by first deprecating and warning a pathspec that has such an element in 2.11 (Nov 2016).
I am not aware of a submodule added directly within a parent repo folder: I always used to add as a parent repo subfolder.
answered Nov 23 '18 at 5:42
VonC
830k28926113157
add a comment |
The path (.) should be a non-existent folder, like Latex-Travis.
Instead, here '.' is interpreted as an empty path (since it is refereing to your parent repo), and as illustrated in ruby-git/ruby-git issue 345:
This really was deprecated since Git 2.1.6:
An empty string as a pathspec element that means "everything" i.e. 'git add ""', is now illegal. We started this by first deprecating and warning a pathspec that has such an element in 2.11 (Nov 2016).
I am not aware of a submodule added directly within a parent repo folder: I always used to add as a parent repo subfolder.
answered Nov 23 '18 at 5:42
VonC
830k28926113157
The path (.) should be a non-existent folder, like Latex-Travis.
Instead, here '.' is interpreted as an empty path (since it is refereing to your parent repo), and as illustrated in ruby-git/ruby-git issue 345:
This really was deprecated since Git 2.1.6:
An empty string as a pathspec element that means "everything" i.e. 'git add ""', is now illegal. We started this by first deprecating and warning a pathspec that has such an element in 2.11 (Nov 2016).
I am not aware of a submodule added directly within a parent repo folder: I always used to add as a parent repo subfolder.
answered Nov 23 '18 at 5:42
VonC
830k28926113157
answered Nov 23 '18 at 5:42
VonC
830k28926113157
answered Nov 23 '18 at 5:42
VonC
830k28926113157
answered Nov 23 '18 at 5:42
VonC
830k28926113157
830k28926113157
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53440570%2fempty-string-is-not-a-valid-pathspec%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
