Perl: the Markov chain saw | |
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
The only final commitment ought to be $ git merge bool_hash. Until then it's pretty easy to git branch -D bool_hash Even if you've merged, you can still rewind without causing grief, as long as you haven't pushed somewhere where others might suffer. I know not everyone's sold on version control tools, but I find them empowering; I can try things without having to remember every change I made along the way. And if a plan comes together, I can merge. If not, cut off the experimental branch with the confidence of knowing that the stable branch is still untouched. If your project hasn't been using VC, it's not too late to start. Assuming it's currently in a working state, initialize a repo, create a "refactoring" branch (probably use a more descriptive name), and get to work. At each major decision, branch, then if it works well, merge. Dave In reply to Re^3: Code cleanup; how best to deal with: defined(%hash) is deprecated at...
by davido
|
|