Hi Robert, I've recently raised the same submodule issue with git-archive you and Lars have in the past. What's the status on your application of the git-archive submodule patch? Have you applied the changes suggested by Lens Lehmann[1]? Your Git fork on GitHub[2] seems to have only applied Lars' patch and an unrelated SVN glob fix... Since you've touched this only last year, I'd like to know where you were at and I can see if I can pick up where you left off (unless you want to finish yourself). Thanks, André [1]: http://comments.gmane.org/gmane.comp.version-control.git/172851 [2]: https://github.com/darconeous/git ---------- Forwarded message ---------- From: Jens Lehmann <Jens.Lehmann@xxxxxx> Date: Fri, Apr 20, 2012 at 4:11 AM Subject: Re: git-archive and submodules To: André Caron <andre.l.caron@xxxxxxxxx> Cc: git@xxxxxxxxxxxxxxx Am 19.04.2012 22:10, schrieb André Caron: > Hi, > > I've recently needed to create a source code archive as part of a > custom build target. This repository uses submodules and I need to > include the submodlule's source code in the archives too. However, > git-archive does not have any option to do so. > > I've taken a quick look at the GMANE mailing list archives and it > seems this provoked quite a discussion in 2009 and that Lars Hjemli > even wrote a patch (in several flavors) for archive.c to include > submodule-aware processing. The lastest source code at > `git.kernel.org` does not contain any traces of this patch (or > submodule aware logic for that matter). The mailing list archives are > not very convenient to browse and I can't figure out what the status > on this submodule-aware git-archive idea is. Has this idea been > completely rejected, or is it still work in progress? The idea is not rejected, this would be a worthwhile addition. It has been brought up again last May, but as far as I know it is stalled since then: http://comments.gmane.org/gmane.comp.version-control.git/172851 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html