Not logged in
Log in now
Create an account
Subscribe to LWN
LWN.net Weekly Edition for May 23, 2013
An "enum" for Python 3
An unexpected perf feature
LWN.net Weekly Edition for May 16, 2013
A look at the PyPy 2.0 release
A proposed Subversion vision and roadmap
Posted Apr 3, 2010 17:26 UTC (Sat) by marcH (subscriber, #57642)
I blame the index
But nothing else. Or is there?
Posted Apr 3, 2010 17:29 UTC (Sat) by Kit (guest, #55925)
Probably the most complex aspect of git I've found is that the official tutorial I used (primarily as a cheat sheet to help me remember the commands) seemed to keep moving locations on the kernel.org server.
Posted Apr 3, 2010 19:29 UTC (Sat) by fperrin (guest, #61941)
mkdir SVN && svnadmin create SVN && svn co SVN .
svn add *.c
Yes, that's more work than git init && git add *.c, but "much harder" ?
Posted Apr 3, 2010 21:37 UTC (Sat) by heipei (guest, #63821)
1. Download some non-versioned source from a website, untar it into dir
2. cd dir; git init; git add .; git commit -m 'initial'
3. work, hack, commit, etc
4. decide that I don't want the history and just rm -rf .git (or the whole dir)
The point is that you don't have two locations for one tiny thing (a repo and a working copy). Also it
works in-place, whereas you have to create the repo with SVN, then checkout the _empty_ repo into
another dir, and then manually copy your files there to add and commit them. Still sounds equally
By the way, if you just want to keep track of very simple changes to a pristine codebase, you can
omit the "commit" in step 2. and just diff against the index. Another tiny thing: Your example
doesn't work (for me), since SVN is too stupid to recognize files without file:/// prepended.
Offtopic svn tricks (was: A proposed Subversion vision and roadmap)
Posted Apr 4, 2010 1:24 UTC (Sun) by cesarb (subscriber, #6266)
Posted Apr 4, 2010 7:35 UTC (Sun) by fperrin (guest, #61941)
Or even simpler, as I did in my exemple, just "svn co file:///$PWD/SVN ." while being in the
directory where you just untar'd the original source. (Or use emacs and `vc-create-repo'.)
>Another tiny thing: Your example doesn't work (for me), since SVN is too stupid to
> recognize files without file:/// prepended.
Yep, I forgot about that. As I did above, replace the checkout step with "svn co file:///$PWD/SVN ."
Posted Apr 3, 2010 22:06 UTC (Sat) by fuhchee (subscriber, #40059)
OK, then how about building (yet another) simple front-end for git?
It does a great job on the back end. If the front end is not simple
enough, build/extend just that.
Posted Apr 4, 2010 15:28 UTC (Sun) by drag (subscriber, #31333)
Posted Apr 5, 2010 4:32 UTC (Mon) by Kit (guest, #55925)
This was exactly my experience. The (crappy) documentation I could find for SVN (I didn't bother with CVS, since it'd already been supplanted by SVN for a while by then) assumed I'd be using SSH or Apache to connect to the repository, and I found the SSH setup to be horribly ugly for a purely local workflow (I didn't even care to bother with Apache, that seemed a bit silly to me).
> boom, boom, and boom. Done.
Those commands are more than enough to get you started on a personal project, and it's fairly simple to pick up the other stuff as your needs expand (I was shocked at how simple branching was... I actually thought I had done it wrong since I'd read so much about how poorly SVN handles it). Plus, being able to make commits even when offline or when you don't want to make them public yet (but you don't want one massive commit containing a crap load of work all over the code base) is easy as hell with git (you just commit and don't push!).
Copyright © 2013, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds