Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Where subversion works well is in providing a centralized versioned filesystem. For many people, that is enough to allow it to be used as a source code repository given a couple conventions (i.e. "trunk, branches, tags" and "don't mess with the tags".)

    Having never been a CVS user, I find svn to be much more approachable and never felt like the tags weren't taggy enough.

    Now, for merging and distributed revision control, git certainly has lots of benefits. But I think it also loses the ease-of-use of svn for browsability and quick checkouts -- at least in the few cases when I've needed to use it. Perhaps there is a way to fetch only a part of the history?

    I would really like to have a mode for "just let me fetch your current code", possibly even using the svn client. Maybe that's easier than I think, but it seems that whenever someone talks about git they start lecturing about the thousands of ways to merge and I end up downloading a tarball and saving versions with `cp`.

    I don't want a lecture -- I'm not having trouble understanding Git for Computer Scientists [eagain.net], but I still haven't seen a "git for those who are just passing through".

    • I totally agree that people explain git unproductively. I've written about that before [manxome.org]. It's definitely possible to say "just give me the trunk head," because gitweb lets you click to get a tgz of it. I don't know what the corresponding git command is, or if (maybe) it isn't exposed with one -- but it is clearly possible and easy. That would be the equivalent to svn export, though, not svn checkout.

      --
      rjbs