Re: git submodule support feedback
- From
- David Lang <david.lang@digitalinsight.com>
- Date
- Apr 26, 2007, 20:59 UTC
- Message-ID
- <Pine.LNX.4.63.0704261358170.9674@qynat.qvtvafvgr.pbz>
- In-Reply-To
- <200704262228.46864.andyparkins@gmail.com>
On Thu, 26 Apr 2007, Andy Parkins wrote:
Show 22 quoted lines
> On Thursday 2007, April 26, Andy Parkins wrote: > >> I'll report further as I come across any stumbling blocks; but here > > The submodule support requires the latest version of git right? That's > going to cause trouble for people running different versions of git > (I've already experienced it in my own limited way - I had to upgrade > all the copies of git I have on my various computers before fetching > and pushing would work). If the repository contains a submodule > reference it effectively becomes inaccessible by a version of git > without submodule support. > > I think that we might be able to avoid that problem though - am I right > in thinking that the problem is that all the tools need teaching not to > follow the gitlink object because that hash doesn't exist in _this_ > tree it is a reference to a commit in another tree. > > Wouldn't it be better if the gitlink reference pointed at an object in > this tree which in turn referred to the submodule commit? That way the > old versions of git would still work with submodule objects in the > repository because they would just see submodules as pointing at a > blob.
if you need to teach your version of git to accept this object that then points to the new tree don't you have to upgrade it to a version that does this? at that pont you could just upgrade to a version that supports them the current way.
David Lang