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.
  • Git's primary advantage, as I see it, is that forks become first-class citizens. Forking is cheap in all good DVCSs, but Git seems particularly strong about not enforcing one central repository with strict commit access.

    I can use git-svn to get some of the benefits of a local Git repo against a centralized SVN repo, but that's a workaround. It's much easier to pull from someone else's Git repo than to apply a series of patches against SVN.

    • I completely agree. For untrusted and non-maintainer forking, it's a world of improvement.

      What I'm curious about is whether this actually results in more changes at the bottom line, or is the flexibility of all this forking largely just something that's nice to have (but won't impact much on the overall progress).