On 6/14/15, Phillip Smith <fukawi2@gmail.com> wrote:
I'm not seeing how that sets up subtrees? The only subtree command in the script is a "push" command.
subtrees are actually part of the repository. They are dynamically created as needed (, which is why I added an option to split and rejoin/save it to save time in the future). That is what is particularly cool about them -- you can just checkout the repo and see a totally vanilla repo, but you can ALSO do interesting things with an exported history. subtree push by default does not leave any visible trace that anything ever happened. Only the pushed-to repo shows something. Like I said, you should be able to pretend it is one vanilla repo, just like many people used to track their AUR3 packages. But .SRCINFO is required for this one, because each folder is *exported* to the AUR4. subtrees are a little confusing at first, because it can be hard to tell they exist! :eek: The master branch of my repo has a bunch of folders with packages. Those are subtrees, but can you tell by looking/inspecting? -- Eli Schwartz