Petr Baudis, Sun, Nov 27, 2005 14:11:47 +0100: > > > >For everyone who have an experience with ClearCase or Perforce (I'm > > > >sorry for mentioning it) it is what the "mappings" are often used for: > > > >a project is build together from different parts, which can be worked > > > >on separately. > > > > > > > >I'm trying to introduce git at work, but have to prepare myself for > > > >possible questions first, and this is one of them :) > > This is something e.g. Cogito wants to support, but does not yet. > Patches welcome. I wouldn't know what to patch, having no clear picture of the approach myself, and especially when I don't feel safe using the solution. For example, how do you go about moving/renaming files between subrepos? Rename detection will not work, which will be unexpected... BTW, how does git-mv behave for out-of-tree renaming? How about inter-repo renaming (remove+add)? > > > It would certainly be nicer to have git ignore directories that have the > > > ".git" directory (so long as it's not the top of the repo, that is), but > > > I haven't had the energy to fix that when there's already a solution > > > that's simple enough and quite adequate. > > > > BTW, will something like "*/.git/*" in info/exclude work? IOW, does * > > match a "/"? > > Nope, but try just '.git' - in case it is not a pathname but just a > filename (or dirname, for that matter), it will recursively apply to all > the subtrees. well, it ignored the ".git"s in the subdirs, not _the_ subdirectories. I think that can be helped by putting the directories themselves into .gitignore lists. - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.htmlReceived on Wed Nov 30 07:49:42 2005
This archive was generated by hypermail 2.1.8 : 2005-11-30 07:49:48 EST