William Papper wrote:

That would be great. I could then add your repo as a submodule, and
someone would just need to pull both for updates. I assume that it
would be pretty easy for you to reset the commits, since only new
versions will be added and there would be nothing in the commit
history you would need to preserve.

  I'd obliterate old commits with

git filter-branch --index-filter 'git update-index --remove filename'

  so the old binaries don't stick around.

Alternatively, if the commits themselves cannot be removed easily, a
new repo could be created for each version. Then, the submodules
reference can just be updated instead of updating the submodule
itself.

  I like the idea of having it all in one repo (or at most divided by language), so that it's easier to maintain/get, and easy for githubbers to track changes to.  Though might change the repository name.

We could also use releases on the tor-download-web repo, and then have
a script download the files for each release automatically. The script
can be updated through git to take care of updating the files.

Which solution seems best?

  Might be good to check in with Runa and Weasel.  Not sure if they're on this list.

~Griffin
________________________________________________________________________
Tor Website Team coordination mailing-list

To unsubscribe or change other options, please visit:
https://lists.torproject.org/cgi-bin/mailman/listinfo/www-team