On Mar 31, 10:16 pm, Thomas Mueller <[email protected]> wrote: > > It would be very great if you'll publish h2 sources in git repo (using > > github) > > switching from svn to git was for sure the best decision I did last year. > > What are the advantages? Many things _could_ be done, but I would > first need a list of reasons _why_ it should be done. I don't > currently have a problem with svn, do you? If yes, what are the > problems?
IMHO, you have a problem with svn, you just don't know. I don't see you using branches, you may think you don't need them in a mostly one- man project, but I use them for my job (a one-man project too) very often. Of couse, with svn they're a real PITA, but with git they work nicely. One day there may be many contributors to h2 and you'll see that managing it using svn gets harder and harder and switch anyway... and you won't understand how you could lose your time with svn. > The disadvantages I know are: Changing to git requires time. The > Eclipse support for git seems to be worse than the svn support. Agreed, but even without _any_ eclipse support it's much better than svn. On Apr 1, 2:54 am, Thotheolh <[email protected]> wrote: > Hi Thomas, I would like to suggest maintaining both a Git and an SVN. I would not. > Yes, it's tedious. But before going into that, here's a few links of > Git vs SVN comparison. > > -https://git.wiki.kernel.org/index.php/GitSvnComparison(Git's own > view) > -http://thinkvitamin.com/code/why-you-should-switch-from-subversion-to... > (Blog post) > -http://stackoverflow.com/questions/161541/svn-vs-git(Stackoverflow > post) > > Back to maintaining a Git and SVN, which is tedious, but could be > theoretically made simpler via shell scripts or some scripts or tools. > A suggestion is to continue using SVN as the main, but every update > onto the SVN, you may want to have a prepared script that would simply > launch on a double click and would grab the latest SVN and clone onto > Git. This isn't very elegant sounding but it reduces the work > overhead. I don't actually see the point for managing both. However, it's quite simple, at the beginning you need maybe 5 command lines (I could write them for you) and then updating the git repo is just git svn fetch && git push # the URLs are stored in the config file made by the 5 lines mentioned above Surely not the most efficient way, but fully sufficient. This way you wouldn't need to learn/use git at all (which isn't good since git is IMHO worth learning). -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
