Nested submodule status bug

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Dear git developers,

still about nested submodules, I stumbled upon the following very strange
behaviour.

1) Make a baz submodule inside a bar submodule inside foo
  mkdir foo; cd foo; git init
  mkdir bar; cd bar; git init
  mkdir baz; cd baz; git init
  touch 1
  git add 1
  git commit -m 'first baz commit'
  cd ..
  git submodule add ./baz
  git commit -m "Add baz submodule"
  cd ..
  git submodule add ./bar
  git commit -m "Add bar submodule\n"
  git submodule absorbgitdirs
  cd bar
  touch 2

2) Now add the following alias:
  subs="! git -C baz status"

3) And run it
  git subs

To get:
~~~
On branch master
Untracked files:
  (use "git add <file>..." to include in what will be committed)
	../2

nothing added to commit but untracked files present (use "git add" to track)
~~~


While when not launched as an alias, `git -C baz status` give the correct
result:
On branch master
nothing to commit, working tree clean


Note: I get the same bug when I use
  subs="! sh -c 'cd baz; git status'"
The bug is only there if absorbgitdirs is used. Also I have to be in an
intermediate submodule.

Best regards,
Damien



[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux