On Mon, Jun 27, 2016 at 1:07 PM, Bart Bogaerts wrote:
> Hi,
>
> I tested this on git version 2.9 and it still fails (exactly the same
> behaviour as on the stackoverflow post; also the workarounded I posted
> there still works).
I see. the commit I referenced was solving a slightly different prob
Hi,
I tested this on git version 2.9 and it still fails (exactly the same
behaviour as on the stackoverflow post; also the workarounded I posted
there still works).
Some output showing the bug follows below:
bartb@EB-Latitude-E5450 ~/Documents/papers $ git status
On branch master
Your branch is
On Sun, Jun 26, 2016 at 11:01 PM, Bart Bogaerts wrote:
> With a repo structured as follows
>
> main-files
> |- submod
> |- subsubmodule
>
> git mv submod newlocation
>
> does not do what it is supposed to do. It actually breaks the git repository.
> It can be fixed easily.
> A complete descrip
With a repo structured as follows
main-files
|- submod
|- subsubmodule
git mv submod newlocation
does not do what it is supposed to do. It actually breaks the git repository.
It can be fixed easily.
A complete description of the bug, including a workaround, can be found on
http://stackoverfl
4 matches
Mail list logo