On Tue, Jun 1, 2010 at 6:00 PM, Daniele Segato <daniele.bilug@xxxxxxxxx> wrote: > On Mon, May 31, 2010 at 10:04 PM, Andrew Sayers > <andrew-git@xxxxxxxxxxxxxxx> wrote: >> On 25/05/10 08:42, Michael J Gruber wrote: >>> >>> Feel free to contribute to the Git Wiki maybe at >>> >>> https://git.wiki.kernel.org/index.php/GitDocumentation >>> >>> in the "User contributed Documentation" section. >>> >>> Michael >>> >> >> Thanks for the hint - this turned into rather more than just uploading a >> PDF, and I've now finished a complete write-up here: >> >> https://git.wiki.kernel.org/index.php/SvnMigration > > > That's a great job! > > I want to point out some difficulties I encountered switching from > Subversion to Git-SVN. > I'd like to discuss them here before, eventually, contributing them to > that page. > > > = Empty directories = > Git do not track directories, it tracks content. That means you'll not > get/commit empty directory in your > working tree. > Sometimes empty directory may be needed by some fancy script or > external software you use with your > project (example, ANT). > > Developers should be aware of this: if they really need to create an > empty directory they can both > create it through subversion both create a "dummy" file in the > directory and commit it, if that's an option. > This has been solved in recent versions of git: git-svn creates the empty directories when you check out. It might not be 100% robust (I'm not saying it isn't robust, I'm saying I don't know if it is), but it works for my setup. > You also can't create new Subversion branches or tags with git-svn, > you'll had to use subversion directly for that. > Incorrect. git-svn have sub-commands called 'branch' and 'tag' for this purpose. -- Erik "kusma" Faye-Lund -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html