I'm not expert enough on this. Since Attila is the one who set up the SVN server, I'll leave further discussion on this up to him. Me, I just want to do whatever is best. :)
On Sat, Nov 7, 2009 at 3:19 PM, Peter Stuge <[email protected]> wrote: > Timothy Normand Miller wrote: >> >> Also, we should not host them in the SVN repo, because the project >> >> file would be a non-ascii blob. >> > >> > I disagree with this. >> >> I agree with your reasoning. The problem is that the server the >> repo is on doesn't belong to us. Since binaries can't be diff'ed, >> then every time you check in an update, it takes up as much space >> as the whole binary. > > Subversion is smarter than that actually. :) > > --8<-- http://subversion.tigris.org/faq.html#binary-files > Note that whether or not a file is binary does not affect the amount > of repository space used to store changes to that file, nor does it > affect the amount of traffic between client and server. For storage > and transmission purposes, Subversion uses a diffing method that > works equally well on binary and text files; this is completely > unrelated to the diffing method used by the 'svn diff' command. > -->8-- > > >> Moreover, a SVN repo, IMHO, is not an appropriate place to keep >> releases. > > Ah! I agree about releases. But obscurely formatted binary files > ("project files" above) that make up the "source" for hardware tools > are good to have in the repo I think. > > > //Peter > _______________________________________________ > Open-graphics mailing list > [email protected] > http://lists.duskglow.com/mailman/listinfo/open-graphics > List service provided by Duskglow Consulting, LLC (www.duskglow.com) > -- Timothy Normand Miller http://www.cse.ohio-state.edu/~millerti Open Graphics Project _______________________________________________ Open-graphics mailing list [email protected] http://lists.duskglow.com/mailman/listinfo/open-graphics List service provided by Duskglow Consulting, LLC (www.duskglow.com)
