You might just want to use git-svn. All the benefits of git locally, and nobody on the other end even needs to know.

Welcome to Git :) You'll soon notice how much more rad it is...

Jeremy,

 Couldn't you just install a local repository, commit to that repository and then re-commit your changes to the master repository when you got back online ?

That's great to hear!  I have been using git for some time (msysGit) and while git-svn is slow (really slow), apart from that I love it.  It really gives a freedom to safely experiment.  You are going to love the cheap branches, shelving, small repo size, etc.

And if you are going to consider using a public git repository for StructureMap might I suggest github.  The ability for people to clone your public repo, make changes in "their" repo and then request you do a pull back to your 'official' repo is just too slick.

Jeremy,

I'd second the git-svn command, this would at least give you everything you need via the git-svn dcommit command until you are able to move the StructureMap repository over to git.  I'd like to hear the migration story from svn to git, I have yet to do that one myself.

my advice would be to keep mercurial in mind as well. in my (admittedly limited) experience, it's a lot easier to deal with on windows than git.

the story may well have changed though, so i dont think starting with git is the wrong move at all.

re: git-svn

I've found the following guide to using Git + SVN to be pretty helpful for getting my head around how the two interact. quirkygba.blogspot.com/.../using-git-with-google-code-hosting.html

I have used mercurial and git, mercurial for more than a year.  I have moved over to git.

The big problem with mercurial in my mind at the time I was using it was the way it did branching.  A branch was a totally separate working copy, effectivly a separate checkout of everything.  When I needed to spike something simple I would have to clone and and then remember to take that copy with me.  It got to be just to much work.

Git is a single repo, with multiple branches (actually just tagged revisions with a particular history).  In all fairness, mercurial may have done something to allow multiple heads (branches) in the same repo but I moved away from it more than a year ago and never looked back.

As for working with git on windows, just install the msysGit installer and open a command line (regular cmd.exe if you have installed it into your path) and have at it.  I use powershell myself but it still works great and I never have to worry about the "msys" part of it because its totally self contained.  And it works on Vista64 which is what I run.  

The way you felt in Missouri is exactly how I feel every time I want to try and make changes to open source code I don't have commit rights to: you make your changes very carefully, very slowly (reverts ) then hold your breath until the maintainer accepts your patches.

Git is freedom from this. Everyone can be a committer and not hurt anyone else. Contrary to what you might think intuitively (that this makes it too easy to stop integrating with others) I think this style of source management promotes shared ownership of code and does a better job tracking and enabling developers communicating via code.

Glad to hear.

I have not tried msysgit yet, I have been pleasantly using cygwin+git for about 9 months now.

These were the links I found helpful when I was getting started

del.icio.us/.../git

Pingback from  Dew Drop - May 16, 2008 | Alvin Ashcraft's Morning Dew

You might want to give bazaar (http://bazaar-vcs.org) a try as well. It supports both fully distributed and centralized workflows, and it's a first class citizen on Windows, not an afterthought port.

Best way to use Git on winbloz is just install cygwin and use git through that - works like a charm.

You will also discover that git provides far more than simply off line commit access.