On 10/22/06, Linus Torvalds <torvalds@xxxxxxxx> wrote:
On Sat, 21 Oct 2006, Aaron Bentley wrote: > > Any SCM worth its salt should support that. AIUI, that's not what Tim > wants. He wants to intermix files from different repos in the same > directory. > > i.e. > > project/file-1 > project/file-2 > project/.git-1 > project/.git-2 Ok, that's just insane.
[snip]
Anyway. Git certainly allows you to do some really insane things. The above is just the beginning - it's not even talking about alternate object directories where you can share databases _partially_ between two otherwise totally independent repositories etc.
Perhaps this is insane, but it does not make sense to track all config files in etc as though they belong in a single repo. Each application/pkg has a set of associated config files. Actually in some cases it is easy to track which files belong in each application/pkg repo. For example dpkg list conffiles per pkg. Additional config files not in the application/pkg maintainer repo branch are easily added to the application/pkg local repo branch. My question is where should file metadata be stored in git? With hook scripts, the file metadata can be captured and applied appropriately. If a similar thing can be done with bzr as Linus described for git, I am all ears. - 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