On Thu, May 24, 2007 at 10:32:32PM CEST, Junio C Hamano wrote: > And she does not have to. She can do the development/fixes in > (temporarily) checked out subproject tree, and push it back to > the .git/subproject/kernel26/ repository in the superproject > before she leaves (i.e. before branch switching at superproject > level needs to obliterate it). The change stored in the > .git/subproject/kernel26/ repository in the superproject can > further be pushed back to its 'origin', be it the true > "upstream", or "the standalone repository for the subproject" I > mentioned above. ..snip.. > It's just bare/pure layout is easier to understand because it is > essentially a "mirror" of the upstream. I OTOH think that it's less confusing to just keep it the same for all the normal repositories - and you yourself did not rule out the possibility to have local changes in the repository, in which case we certainly should use the separate-remotes layout or we go back to last year's refs mess. -- Petr "Pasky" Baudis Stuff: http://pasky.or.cz/ Ever try. Ever fail. No matter. // Try again. Fail again. Fail better. -- Samuel Beckett - 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
