Jan Harkes <jaharkes_at_cs.cmu.edu> writes:

>> You are saying "the development tree", which I don't follow.  Surely
>> when releasing 2.6 of lwp then the lwp repo gets a tag, since it is
>> primarily an independent project.
>
> Git tags are associated with the commit object, which in turn points a
> the tree. So the development tree would consist of the whole of
> coda/lwp/rpc2/rvm at the point in time that the tag is created.

But for a tag that is of an lwp release, that's odd.   If the tag is
lwp-2.6, and it is understood to only refer to the lwp piece, then that
sounds ok but still odd.

>> So it might be that coda.git is the independent version, and there's a
>> coda-meta.git that pulls all of them in as submodules.  That seems much
>> cleaner.
>
> Well, except that I'm trying to get away from using submodules. But it
> may be moot because I just seem to hit problems in reposurgeon and the
> git filter branch history rewriting afaik doesn't do what I would like.

But if you don't use submodules, then either you have everything in one
repo, or things are handled separately, which is the divide I mentioned
before that you said wasn't really a divide because of submodules :)