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
an endless discussion thread about what features to include.
-- Jarkko Hietaniemi
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
go with git, or with subversion, it's all the same (Score:1)
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.
Bill
# I had a sig when sigs were cool
use Sig;
Re: (Score:1)
Subversion makes the mental overhead of creating a repository very much greater than any DVCS, where you just say
git initorhg initorbzr initor whatever you prefer – there’s no need to pick a place for you repository, it just goes wherever your working copy is. There’s also no need to turn the current directory into a working copy after checking it in initially by checking it right back out, which may in turn require casting a path to a URL (sincesvnadminonly works locally).It seems
Re: (Score:1)
i see your point that if you have just a tarball of source, creating a local repository easily is good. Needing a cheat sheet for creating
Bill
# I had a sig when sigs were cool
use Sig;
Re:go with git, or with subversion, it's all the s (Score:1)
Sure, but you have to do it. Subversion does not (and by its nature as a centralised system cannot) provide a useful default for you, so everyone needs to establish their own convention and then script the sequence to their preferences. That’s obvious blinking twelve territory.
Reply to This
Parent