Share on Twitter

Today I was supposed to deploy some changes on company static website made by web designer. The website source is hosted using SubVersion (SVN). I thought it’ll be great if I can export just the changes he did with their folder structure and without asking him to do anything extra, and deploy that.

 

Here are the steps using TortoiseSVN:

  1. Right Click The working, choose TortoiseSVN => Show Log
    image
  2. Since he used multiple revisions, I selected the those revisions, right clicked, and chose “Compare revisions”
    image
  3. Selected all files, right click, and choose “Export selection to…”
    image
  4. Simply choose the destination folder from the folder selection dialog that comes up, and here we go.

 

That was very quick hint, but hopefully helpful to someone. I’m sure there must be other ways to do it also BTW, but this was the quickest to try with an empty head.

Share on Twitter
, , , ,
Share on Twitter

The SVN News

Today I was hanging around GitHub when realized a relatively old news, dated to April 1, 2010, saying they do support SVN.

Announcing SVN Support

Yes, it’s April Fools day. Very funny date to announce anything serious as they admit themselves in an update to the news post, but it DOES work.

Use the same Git clone HTTP URL, just add “svn.” between “http://” and “github.com”:

http://svn.github.com/[user]/[repository]

It even allows you to write changes back to the repository, as announced in the more recent news post, dated May 4, 2010, check it out for the “cavets” (known issues):

Subversion Write Support

That uses the same URL but with HTTPS:

https://svn.github.com/[user]/[repository]

This should work best when you want to get some project for read-only access or very few commits from your side, when this project has a very long history you are not really interested in. Of course you wouldn’t want to use that if you are leading (or a main committer to) a project hosted at GitHub.

, , , , , , , ,