>> Probably it's "read" which does backslash expansion, but nothing else.
>> Just grepping git-submodule.sh, some of the "read" calls should probably
>> be "read -r" (I also don't know how some of those loops would cope with
>> a submodule name that needed quoting).
>
> So I blindly converted all "
On 04/07, Jeff King wrote:
> On Fri, Apr 07, 2017 at 08:12:49AM +0200, Joachim Durchholz wrote:
>
> > So... something inside "git submodule add" is replacing the \b with a
> > backspace control code.
> > [...]
> > Whatever that "something" is, it is not doing shell expansion, otherwise it
> > woul
Am 07.04.2017 um 08:30 schrieb Jeff King:
I also don't know how some of those loops would cope with
a submodule name that needed quoting).
"git submodule add" worked fine with most of the following names:
"sub"
# potentially confusing the shell
"sub with blanks",
"sub with\nnew
Am 07.04.2017 um 08:30 schrieb Jeff King:
Probably it's "read" which does backslash expansion, but nothing else.
Just grepping git-submodule.sh, some of the "read" calls should probably
be "read -r"
http://wiki.bash-hackers.org/commands/builtin/read has this to say:
Essentially all you need t
On Fri, Apr 07, 2017 at 08:12:49AM +0200, Joachim Durchholz wrote:
> So... something inside "git submodule add" is replacing the \b with a
> backspace control code.
> [...]
> Whatever that "something" is, it is not doing shell expansion, otherwise it
> would have started an interactive calculator
Hi all,
I'm having a problem with submodules that reside in directories that
(unwisely) contain a backslash in their name.
Transcript:
### Arrange
$ git init main
Initialized empty Git repository in /tmp/test/main/.git/
$ git init sub\\with\\backslash
Initialized empty Git repository in /t
6 matches
Mail list logo
