Thanks. I just don't get how to do it though.. I remember having trouble signing up with Github and they wanted be to produce some code, then I realised it wasn't necessary for sign up, but its similar to the Terminal instructions given here at GC. Very confusing so I think I'll ask the programmer to upload it next time, this time I only asked for the code because I thought it would be easy to upload. Not so.
On Jan 1, 5:11 am, Ben Collins-Sussman <[email protected]> wrote: > On Thu, Dec 31, 2009 at 9:45 PM, tenderhooks <[email protected]> wrote: > > It looks like a lot of work, why cant I just upload the files in a > > tree structure (like they are on my HDD already) and then leave it at > > that. > > Looks like you just did. The 'downloads' section now has a 5MB .zip > file. Even though the 'downloads' section is usually used for > distributing releases or executables, it's perfectly acceptable for > distributing source code as well. However, it's going to be harder > for other people to collaborate with you. Your source repository is > still empty, which means passers-by can't easily browse the source > code or see the history of changes. To collaborate, they'll have to > download the .zip, which is a higher barrier to entry. (And there > won't be a central repository for sharing changes easily either.) No > big deal, though -- a lot of folks just throw up a .zip file when they > want to toss code out there quickly. > > > I sincerely do not get this and am surprised there is no YouTube > > tutorial or video of any kind explaining any of this. > > That's because version control is used by every software developer -- > just like compilers, debuggers, text editors, etc. It's like coming > to a carpentry website and asking why there are no videos explaining > how to use hammers. :-) I've already pointed you to the standard > book on Subversion (which has a general theory intro as well as a > 'quick start' appendix); if you search google, you'll find a zillion > blog posts explaining how to get started with version control as well. > > In a nutshell, version control is about storing your code in a shared > database so changes can be tracked. Yes, it's more work than just > tossing .zip files around. But it's also way more useful. -- You received this message because you are subscribed to the Google Groups "Hosting at Google Code" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-code-hosting?hl=en.
