Jakub Narębski wrote: > Hmmm... I used to do (and still do) such not-recommended thing, > i.e. keeping git/gitweb/TODO etc. in git/gitweb/.git repository, > while having git/gitweb/gitweb.perl in git/.git repository. Why don't you put the gitweb/TODO in a different branch in the git.git repository? Why do you feel the need to have two different repositories tracking different files in the same path? Just out of curiosity, how does stuff work with your setup? Does the worktree gitweb/ belong to your gitweb.git repository or git.git repository? How do half the git commands work? For example, won't git clean -dfx remove the files tracked by your other repository? Will a conflicting checkout not stomp files tracked by the other repository? How are worktree-rules like .gitignore applied? > So my (admittedly strange) setup will stop working? Yes. I would persuade you not to use such a gross setup; this is not what git was intended for at all. -- 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