Beefy Boxes and Bandwidth Generously Provided by pair Networks
Don't ask to ask, just ask
 
PerlMonks  

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

In my opinion, the real power of SVK is that it gives you personal version control, while integrating easily with a master repository. It does this by letting you make a local branch that you can check-in to without affecting the master repository.

svk cp //foo.bar/svn //local/foo.bar/svn svn co //local/foo.bar/svn

From that point, you can check-in your work incrementally while working totally offline on your own private branch. This is pretty important if you practice test-driven development -- after each new test passes, check in the code.

After reconnecting to the network, you can pull down changes from the master, resolve any conflicts, and push (merge) your changes back upstream.

# while on the network svk pull # go offline and do your work # reconnect to network and get any updates svk pull # resolve conflicts # merge changes back upstream svk push

I often work on my laptop on planes or other places without connectivity and this rocks. Even when I'm on the network, I generally use a local branch as it's really fast to check-in. It's like coding with a safety net.

-xdg

Code written by xdg and posted on PerlMonks is public domain. It is provided as is with no warranties, express or implied, of any kind. Posted code may not have been tested. Use of posted code is at your own risk.


In reply to Re: SVK by xdg
in thread SVK by rinceWind

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others cooling their heels in the Monastery: (6)
As of 2021-06-12 18:41 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    What does the "s" stand for in "perls"? (Whence perls)












    Results (53 votes). Check out past polls.

    Notices?