Subtree independancy

Hi there!

I’m an amateur composer, using Lilypond (programming language). Having one repository for each musical piece was not what I wanted. Then, searching Git help pages, I found subtree merge. I did that and it worked fine, but now I have these other questions, for which I couldn’t find the answer.

  1. So I have all the musical pieces duplicated, existing both in the original repository and in the merged subtrees. Now, if I delete the original repositories, will it affect the merged subtrees? Can I regard the subtrees as the sole workspace and discard the originals?
  2. When I start to compose my next piece, is there a way to create it directly as a subtree, without having initially a separate repository to be again duplicated when it’s merged afterwards?

Thanks,

Cássio.

P.S.: None of the subtrees have a .git directory; only they appear as remotes in the main repository’s config file…

Since I posted this, I noticed that the config file of the base repository refer to its subtrees’s remotes as in this example:

[remote "contraponto"]
	url = https://github.com/cassio-tav/contraponto
	fetch = +refs/heads/*:refs/remotes/contraponto/*

Am I wrong to read this as meaning that the subtree still depends on the original repository “contraponto”? In that case, to get the behavior I’m looking for (the subtree working kind of like its own subrepository), would it work to edit the config file to make the subtrees’s directories the remote repositories? That is, pointing the “contraponto” remote to the corresponding subtree in the base repository “lilybag”, like so:

[remote "contraponto"]
	url = https://github.com/cassio-tav/lilybag/contraponto
	fetch = +refs/heads/*:refs/remotes/contraponto/*

Would that have any unwanted, negative side-effects?