Hi, Coming back to you with some updates. I understand finally interest of difference between 'from' and 'at'. The point is: is it a bug if the 'git status' provide the origin/HEAD instead of HEAD SHA1? If you want a test case with screenshots, let me know. Regards, Laurent _____________________________________________ From: FIGADERE, LAURENT Sent: Thursday, September 20, 2018 3:26 PM To: 'git@xxxxxxxxxxxxxxx' <mailto:git@xxxxxxxxxxxxxxx> Subject: git status - difference between from and at Hi guys, Recently I used git on a top repository which integrated few other submodules. The 'git submodule' command provides the right information on SHA1 used for each submodule. When I 'cd' into a submodule and run the command 'git status', I got this message: HEAD detached from 55846b8 nothing to commit, working tree clean Which was not the right checked out SHA1: it should be 2422597 I verified in a git log command, and I was using really the '2422597' SHA1 and not 55846b8. The command: git log --graph --oneline --abbrev-commit --all Output: * 55846b8 (tag: 01.050.002, origin/master, origin/HEAD, master) ... * 2422597 (HEAD) ... After running : git co master cd .. git submodule update I ran again git status command inside the submodule. This time, I got this message: HEAD detached at 2422597 nothing to commit, working tree clean First question: do you confirm that 'HEAD detached FROM' provides the SHA1 of origin/HEAD? And 'HEAD detached AT' provides the SHA1 we are using : HEAD? Second question: what is the goal of such information? Because from my opinion it can be difficult for end users to understand what SHA1 they are using in the submodule. Thanks by advance for you feedbacks. Regards, Laurent Figadere
