On Mon July 22 2019 09:18:47 Slávek Banko wrote: > I can confirm that it works. If the git repository already exists in the > destination folder, then call "git submodule init" uses this repository > and will simple write the information to the ".git/config" file in the > master repository. As a result, the only difference is that "scripts/.git" > will not just be a file, but a regular git folder - the same as it would > be in ".git/modules/scripts" if the initial cloning would be done using > git submodule init + git submodule update. And this is no problem at all, > everything works fine. After all, in this way the submodules were placed > in older versions of the git. If anyone wants convert the scripts submodule afterwards to match the others they can "git submodule absorbgitdirs". --Mike --------------------------------------------------------------------- To unsubscribe, e-mail: trinity-devel-unsubscribe@xxxxxxxxxxxxxxxxxxxxxxxxxx For additional commands, e-mail: trinity-devel-help@xxxxxxxxxxxxxxxxxxxxxxxxxx Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
