On 03/28/2011 08:08 AM, Alexander Graf wrote:
It depends on how often the code changes. If it changes regularly and qemu is
expected to take in newer versions, then we need to record which slof version
comes with which qemu version. Submodules do just that.
A commit id / tag in the README document it pretty well, no? Also, a README
file is human readable. Submodules don't really buy anyone anything.
When I do a release, I do the equivalent of:
git submodule update --init
rm -rf roms/*/.git
rm -rf .git
Having the information is submodules makes this process automated and
repeatable.
The main motivation is that we need to ship source for any binary we
include in our tarball.
Regards,
Anthony Liguori
