On 16 January 2012 10:09, Holger Hellmuth <hellmuth@xxxxxxxxxx> wrote: > On 14.01.2012 21:59, Hilco Wijbenga wrote: > Take a look at the rather simple script git-new-workdir (everything > important happens in the last 20 lines). It just makes logical links to all > files (mostly directories) under .git except three files that relate to the > index (mainly the index file itself and HEAD) Yes, I did that but I cannot figure out from that why I see lots of files and such staged for commit on master when I almost never work on master. I only use master to pull in upstream and to merge in one of my branches and push. So unless I'm doing that, I would expect "git status" to not output anything. > That would suggest that normal git operations operating on files in those > directories happen identical whether you are in the root repo or in any of > the satellites. Only where the whole repo is acted upon (git clone, cp/rsync > or deletion of the whole repo) the root repo would be "special". That all makes sense to me and is what I was expecting. So why is "git status" on master displaying anything? Here is what I see: In my working directory: hilco@centaur /mnt/lacie/workspaces/my-project-master my-project-master (master $ u=)$ git status # On branch master nothing to commit (working directory clean) In the shared repo: hilco@centaur ~/git-clones/my-project my-project (master +$ u=)$ git status # On branch master # Changes to be committed: # (use "git reset HEAD <file>..." to unstage) # # deleted: .gitattributes # modified: .gitignore # new file: ... ... hundreds more ... Is this related to my use of a symlink? I have a symlink "~/workspaces" pointing to /mnt/lacie/workspaces/. Is that somehow affecting things? -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html