Slash Boxes
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.
More | Login | Reply
Loading... please wait.
  • with apologies to Miguel de Cervantes, Pierre Menard, Joe Darion, and Sophia Loren/Sheena Easton ...

    the workflow with subversion would be the same, except the default output of 'svn diff' is usable by patch, so no special command needed.

    I used the equivalent of svn diff | ( cd $newdir; patch) just the other day to propagate changes from a local svn tree to one built with https login & comit bit.

    # I had a sig when sigs were cool
    use Sig;
    • How would you do this in Subversion without maintaining a repository? Maybe you can, but I just don't know how.

      • use someone else's repository? :-)

        a local repository of any sort ... even old sccs/rcs ... is always a good idea for hyper-meta-undo, if for nothing else. if git is better for that than svn, that's interesting news.

        see also answer to Aristotle's similar question.

        # I had a sig when sigs were cool
        use Sig;
        • That is exactly what git (or any other DVCS for that matter) is so good for. :-)

          In fact, that’s something I’ve said a couple of times – that DVCSs represent a backtracking to what local-only systems like RCS offered, and a move forward from there in the opposite direction for cross-host collaboration from the one that CVS and its offspring Subversion took. Instead of layering collaboration onto RCS by moving the repository out of a subdirectory of the working copy and behind a networked dæmon, they instead provide for reconciliation between many different copies of the repository. This turns out to be much more powerful.