Re: make a changeset without network connection

If you don't want to make a local branch you can also commit to the  
mirrored path with the --patch NAME switch.  Rather than committing  
the change, this will produce a patch which you can then later apply  
to the trunk, or email to someone who can or even apply to a local  
branch later on if you decide you want the after all.

Michael


On Jul 23, 2005, at 8:12 AM, Russ Brown wrote:

> solo turn wrote:
>
> > thanks a lot!
> > what is the (technical?) reason behind making a local branch?  would
> > it be not more logical for the user to:
> > * just commit to trunk, svk does not write it to the main rep if  
> > there
> >   is no connection
> > * when having a connection again, you do a "svk sync". this
> >   smerges the changes in main rep to your local depot and commits
> >   the result to the main rep.
>
> No, you can't commit to a mirrored path if you have no connection  
> to the mirrored repository, as SVK commits the change to the  
> repository first before syncing the change back into the depot.
>
>
> > -solo.
> > On 7/22/05, Stig Brautaset <stig@xxxxxxxxxxxxx> wrote:
> >
> > > On 22 Jul 2005, at 10:20, solo turn wrote:
> > >
> > >
> > > > is it possible to make a changeset without network connection?
> > >
> > > Yes. In fact, it's one of the major reasons for svk's existence.
> > >
> > > make a local branch (read up on the website). Check out from that
> > > branch, commit to it, then, when you're online again, do svk push.
> > >
> > > Stig