> From: Les Mikesell [mailto:lesmikes...@gmail.com] > > Not sure what you mean about with sparse and recursive checkouts or > why you'd start with /. If there is one project in the repository > you would normally just check out /trunk. Or with multiple projects, > /project_name/trunk.
... see below... > You can have multiple checkouts that don't really affect each other, Yes, that's what I'm talking about. I know I can do this: mkdir trunk ; svn co $URL/trunk trunk mkdir eharvey; svn co $URL/branches/eharvey eharvey But I prefer to do this: svn co --depth=immediates $URL svn update --set-depth infinity project/trunk svn update --set-depth immediates project/branches svn update --set-depth infinity project/branches/eharvey Because in the latter "sparse" checkout, all the directories retain some context about the directories around them, and I can issue a single "svn update" at the top level in order to update both, and I won't get confused about the path relation between two independent checkouts, while I'm browsing around my local filesystem, and stuff like that. But as far as branching/merging is concerned, it's functionally equivalent.
