Sergio Callegari wrote: > Hi, > > once a sub-project has been rewritten by filter branch, there is a problem with > references in superproject. > > This is obviously a case where something "has been published" so filter-branch > is not a good idea. However, super-projects are a very special case of > publication since they might be "in full control" of whom did the rewriting of > their submodules. > > Is there a way to filter branch the superproject so that whatever commit is > referenced that is in refs/original/something in the subproject gets updated to > the corresponding rewritten commit (or an error is given if such a > correspondance does not exist)? > > Namely, can filter-branch on the subproject deliver a "commit conversion table" > that can then be fed to a filter-branch in a superproject? > > -- > 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 > If I recall correctly, submodule was recently enabled to reference a soft label, like a branch name, instead of an hard UID. Look it up in the newest git. But your post brings up another concern. The HEAD referenced by the superproject does not have any hold in the subproject. So if the subproject under-gone a git-gc the reference UID might disappear, as in your case. I wish the git-submodule command would create a TAG or BRANCH in the subproject of all referenced HEADs, so they will not disappear in future maintenance of the subproject tree. (And it could be very informative when viewing in gitweb). The subproject TAG name could, for example, be the commit and date of the superproject's submodule commit. Boaz -- 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
