On Mon, 2008-03-17 at 07:26 -0500, Aaron Spike wrote:
One of the nice things about TortoiseSVN: when you do an SVN update, you can press the view log button that then shows *only* the log of revisions since the last svn update. This way it is very easy to keep track of what changed recently. Since the log UI of tortoisesvn is quite nice, you can see which files changed click on it to see the diff. Makes for easy reviewing when one wants it (I often check files of which I know the code), but does not demand reviewing.
I think the workflow for a DVCS is a bit different. For example I keep one branch to track the state of the main repo and another branch for each task I'm currently working on (branches rather than separate checkouts). Now I can update the state of the tracking branch as often as I want (independently of my working branch, like you are used to in svn). And because the system knows which revisions are in which branches I can check the log at anytime and get just the new commits by comparing the commits on each branch. In git the command for this is called `git whatchanged`. Also one of the things I noticed is that any use of the log functionality in TortoiseSVN was unbearably slow because it requires network access. A DVCS stores all this information locally, so the logs become much more useful and accessible. I think you'll appreciate this.
I'd agree with this, but I'll also note that it makes you lazy when you're trying to work with SVN at the base. I think Bryce was very unhappy when I sent a large patch for 0.46 and while it was broken into nice easy chunks on my branch I had no way to communicate that easily for integration into SVN.
This is also the reason that I'd like to have hosting available. I'm sure I could set up my git hosting, but I'd prefer not to. Sometimes I am working on things that other people would be interested in, but it stays on my computer because it's simpler that way. Being able to push stuff out there before committing it to the main repository would help my workflow.
I'll also comment (in a way that will probably get lost in this thread) that we need to give some lead time before a switch. Right now my SVK branch has changes on it, and I don't think any solution we choose will import from SVK nicely :) So, I need to finish and merge them before we switch.
--Ted