tag:blogger.com,1999:blog-8260739278874294486.post3989555306797969111..comments2021-12-16T15:28:31.042-08:00Comments on Tsuna's blog: Learning git-svn in 5mintsunahttp://www.blogger.com/profile/06114951663056205324noreply@blogger.comBlogger24125tag:blogger.com,1999:blog-8260739278874294486.post-43593942382064015662013-08-14T13:38:09.071-07:002013-08-14T13:38:09.071-07:00how to avoid git to bring all the histories and fi...how to avoid git to bring all the histories and file that do not even exist in repositories and just coming because they have been maintained in histories.<br /><br /><br />http://techidiocy.com/understand-git-clone-command-svn-checkout-vs-git-clone/dare to winhttps://www.blogger.com/profile/15354945152571512422noreply@blogger.comtag:blogger.com,1999:blog-8260739278874294486.post-7254304188890328702012-09-17T10:03:05.272-07:002012-09-17T10:03:05.272-07:00I've used git-svn against two different >1 ...I've used git-svn against two different >1 GiB SVN repositories, and in both cases the git repo was the same size or slightly smaller than a single SVN checkout...mikehttp://mike-warren.comnoreply@blogger.comtag:blogger.com,1999:blog-8260739278874294486.post-24851604439309587402011-10-16T01:30:09.970-07:002011-10-16T01:30:09.970-07:00More than four years on, this article is incredibl...More than four years on, this article is incredibly useful. Thanks!ambarnoreply@blogger.comtag:blogger.com,1999:blog-8260739278874294486.post-79330030168591160832011-04-21T07:55:27.303-07:002011-04-21T07:55:27.303-07:00If anyone are still looking for resources on worki...If anyone are still looking for resources on working with git-svn, I've collected a bunch of how-tos and screencasts here:<br /><br />http://www.tfnico.com/presentations/git-and-subversion<br /><br />Hope you find them useful :)Thomas Ferris Nicolaisen https://www.blogger.com/profile/17464665832399025601noreply@blogger.comtag:blogger.com,1999:blog-8260739278874294486.post-92062776664860778112010-11-23T10:13:49.269-08:002010-11-23T10:13:49.269-08:00Reid, a few years ago I wrote a script that behave...Reid, a few years ago I wrote a script that behaves like the "SVN" command but can also use Git under the hood: http://repo.or.cz/w/svn-wrapper.git<br /><br />It's not maintained and hasn't been used in like 3 years but if you really need something that provides a SVN-cli for Git, maybe you could use it as a starting point.tsunahttps://www.blogger.com/profile/06114951663056205324noreply@blogger.comtag:blogger.com,1999:blog-8260739278874294486.post-59432941061109346342010-11-23T10:11:10.339-08:002010-11-23T10:11:10.339-08:00This is an 3-year-old posting, but it comes up in ...This is an 3-year-old posting, but it comes up in Google searches, so I thought I would point out that there is now a Tortoise-git:<br /><br />http://code.google.com/p/tortoisegit<br /><br />I was looking to see if there was a wrapper for git to make it look like svn, perhaps even to the point of working correctly with scripts, etc?Reidhttps://www.blogger.com/profile/06524801697698851267noreply@blogger.comtag:blogger.com,1999:blog-8260739278874294486.post-17353577496481153372009-04-07T16:22:00.000-07:002009-04-07T16:22:00.000-07:00I have the same issue: Checksum Mismatch.I have the same issue: Checksum Mismatch.Scott Stouthttps://www.blogger.com/profile/07456299717825348137noreply@blogger.comtag:blogger.com,1999:blog-8260739278874294486.post-54945808434165804552009-03-26T05:18:00.000-07:002009-03-26T05:18:00.000-07:00Hi,I've just started using GIT this week, currentl...Hi,<BR/><BR/>I've just started using GIT this week, currently the project i'm working on is held in subversion. I tested git svn clone with a small test project (about 10 files) which worked a treat.<BR/><BR/>This morning i decided to test the clone with the full project i'm working on (11,000 files) and I get the error message Checksum mismatch: vn2.sln 0f7a82f1d38b819 expected: fde799e5ba0d1d07e6b539016bea3260<BR/>got: e71db1010a0da06ea76d4163c452df72<BR/><BR/>Can someone help with why this error is happening? Is there an issue with the GIT clone and large repositories?<BR/><BR/>Thanks in advance for your help,<BR/>G.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-8260739278874294486.post-78879803180560907752009-01-30T00:55:00.000-08:002009-01-30T00:55:00.000-08:00Hi,Nice introduction but i've got a problem,I ...Hi,<BR/>Nice introduction but i've got a problem,<BR/>I execute :<BR/>git-svn clone -s --username=fabien.engels http://myserver/svn/myproject destination_directory<BR/><BR/>During the cloning process, i can see message like this one :<BR/><BR/>Found possible branch point: http://myserver/svn/myproject/trunk => http://myserver/svn/myprojecy/tags/0.5, 88<BR/>Found branch parent: (tags/0.5) e45cd56cca1ee72417af0c3b83244fcfc6ce5978<BR/><BR/>But when i go inside my destination directory and i execute git tag -l, i got nothing like git don't see my tags.<BR/><BR/>Is it ok ? or i messed something ? :)Fabien Engelshttps://www.blogger.com/profile/06833469934127507658noreply@blogger.comtag:blogger.com,1999:blog-8260739278874294486.post-31581312179825376992008-10-24T22:41:00.000-07:002008-10-24T22:41:00.000-07:00I always like to add --prefix=svn/ when I'm clonin...<I>I always like to add --prefix=svn/ when I'm cloning git repositories</I><BR/><BR/>Consider adding some color to your branches as well via: git config --global color.branch autoAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-8260739278874294486.post-70120966368818038942008-07-08T17:08:00.000-07:002008-07-08T17:08:00.000-07:00@Anonymous: wow, thanks for your feedback eighty-p...@Anonymous: wow, thanks for your feedback eighty-percenter. Go back to your desk and struggle for a day to understand some verbose api so you can spend another 3 days getting some glue code to work that a twenty-percenter wouldn't even bother factoring in to the time needed for a larger task.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-8260739278874294486.post-74761739268720236602008-06-06T11:08:00.000-07:002008-06-06T11:08:00.000-07:00I always like to add --prefix=svn/ when I'm clonin...I always like to add --prefix=svn/ when I'm cloning git repositories - it's nice to have the branches prefixes and gets rid of the "ambiguation" errors if you're like me and create local branches for each of your subversion branches.Tim Harperhttps://www.blogger.com/profile/03349408198556972919noreply@blogger.comtag:blogger.com,1999:blog-8260739278874294486.post-76690617389967514392008-03-04T03:10:00.000-08:002008-03-04T03:10:00.000-08:00Samuel, I think it is you that misread the manpage...Samuel, I think it is you that misread the manpage. Or maybe the behaviour of -a has changed recently. <BR/><BR/>OPTIONS<BR/> -a|--all<BR/> Tell the command to automatically stage files that have been modified and deleted, <I>but new files you have not told git about are not affected</I>.<BR/><BR/>(emphasis is mine)<BR/><BR/>this clearly states that files not added by "git add" will /not/ be commited. Thus, "git commit -a" is the closest thing to subversion's commit.<BR/><BR/>Philippilifhttps://www.blogger.com/profile/09800128178202559373noreply@blogger.comtag:blogger.com,1999:blog-8260739278874294486.post-65135761680765166962008-03-03T14:40:00.000-08:002008-03-03T14:40:00.000-08:00@setok: I suggest you read the git-commit manpage ...@setok: I suggest you read the git-commit manpage again. The -a flag tells commit to automatically seek out modified files, new files, etc. and automatically git-add them first. It's behavior is most definitely NOT equivalent to "svn commit".<BR/><BR/>Just clearing up a common misconception.Samuel A. Falvo IIhttps://www.blogger.com/profile/11523132404727383627noreply@blogger.comtag:blogger.com,1999:blog-8260739278874294486.post-18585406873933213432008-01-30T12:08:00.000-08:002008-01-30T12:08:00.000-08:00It is not true that git commit -a will schedule fi...It is not true that git commit -a will schedule files that it does not know about. You still have to add them first with "git add". Essentially git commit -a is similar to "svn commit" and is actually what I normally use.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-8260739278874294486.post-38443851810006194842007-10-22T12:48:00.000-07:002007-10-22T12:48:00.000-07:00The project now has 1809 revisions and my working ...The project now has 1809 revisions and my working copy weights roughly 4M, my .git is also about 4M after a 'git-gc --prune --aggressive' and I have an additional 1.3M of meta-data for git-svn under .git/svn. Anyways, it's quite common to have .git repositories with the entire history of a project that weight less than an actual working copy. The point is, people are usually afraid of the space consumed by the repository whereas they shouldn't.tsunahttps://www.blogger.com/profile/06114951663056205324noreply@blogger.comtag:blogger.com,1999:blog-8260739278874294486.post-31033727985265081082007-10-22T12:39:00.000-07:002007-10-22T12:39:00.000-07:007.6M to 6.6M? Something must be wrong. Did you r...7.6M to 6.6M? Something must be wrong. Did you run git-gc ?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-8260739278874294486.post-47605737629065779372007-10-21T23:22:00.000-07:002007-10-21T23:22:00.000-07:00That's not true, Git comes with many graphical use...That's not true, Git comes with many graphical user interfaces available on Windows. The official distribution is msysGit, it comes with git-gui and gitk. There is also qgit. These are only 3 of them but I know there are others. I admit that most of them are still in "beta" stage, although they are usable, and Git probably doesn't promote them enough, but saying that it's only for ultra-nerds that don't work with Windows or that it needs to be scripted to be brought in usable state is total rubbish. It clearly shows that you did not really bother to try Git.tsunahttps://www.blogger.com/profile/06114951663056205324noreply@blogger.comtag:blogger.com,1999:blog-8260739278874294486.post-2119902615541027382007-10-21T22:15:00.000-07:002007-10-21T22:15:00.000-07:00Point against git: there is no TortoiseGit for it ...Point against git: there is no TortoiseGit for it on Windows, and thus, only ultra-nerds use it. This is something only supportable for nerds, and not for users in a commercial environment. Everything can be scripted and be brought into a usable state, but this is something only the nerds want to do. Other users just want to use an SCM system, and not masturbate over the greatness of their version control system of the day.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-8260739278874294486.post-24298647632633866502007-09-12T07:46:00.000-07:002007-09-12T07:46:00.000-07:00Wow... bravo article!!I'm doing all my Subversion ...Wow... bravo article!!<BR/><BR/>I'm doing all my Subversion work in git right now :)Hendyhttps://www.blogger.com/profile/06090262953224426246noreply@blogger.comtag:blogger.com,1999:blog-8260739278874294486.post-15262333231734673252007-07-26T14:02:00.000-07:002007-07-26T14:02:00.000-07:00That's true, but that's a real point in favor of G...That's true, but that's a real point in favor of Git. I had many of these endless discussions and I'm sure at least some of them could have been avoided with a distributed model.tsunahttps://www.blogger.com/profile/06114951663056205324noreply@blogger.comtag:blogger.com,1999:blog-8260739278874294486.post-59362168089352006012007-07-26T13:45:00.000-07:002007-07-26T13:45:00.000-07:00"Git makes it a lot easier for everyone to contrib..."Git makes it a lot easier for everyone to contribute. No endless delicate political discussions about commit access, people pull changes from each other, usually from the people they trust. Everyone maintains their own branches and publish only what they want to publish."<BR/><BR/>A pointless idea on a git-svn tutorial. And Linux is the only project I know of that does this... and it has more politics then most.Ian Monroehttps://www.blogger.com/profile/16953610792430204523noreply@blogger.comtag:blogger.com,1999:blog-8260739278874294486.post-88362693049746866512007-07-19T08:30:00.000-07:002007-07-19T08:30:00.000-07:00#To sync with svn the other way round:#fetch chang...#To sync with svn the other way round:<BR/><BR/>#fetch changes<BR/>git svn fetch<BR/><BR/>#put fetched changes in your working branch<BR/>git svn rebaseAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-8260739278874294486.post-75208151013012250522007-07-19T06:02:00.000-07:002007-07-19T06:02:00.000-07:00For the snv:external stuff the second step/grep ca...For the snv:external stuff the second step/grep can be replaced by: git checkout `git svn find-rev r1000`Anonymousnoreply@blogger.com