interesting, i came across the same problem. we can't access
the corporate svn repos outside the office, and sometimes when
deploying or not working there it's convenient to at least be able to
commit.
i'll explore the svk and the bazaar modules solutions. what is the
complete name for them? perhaps bzr-svn?
for reference, follows what i do, which is a bit cumbersome :)
* after committing, svn export + tar.bz2
* at the foreign computer, untar and cp -r over the bzr repository
* bzr commit, making sure the message contains the svn revision number
* edit / compile / test / bzr commit as needed (loop)
* bzr export => bring to the corporate computer
* for each significant bzr revision, bzr export, cp -r, svn commmit
it's a bit annoying, but it's easy to script or automate with the bash
history. i don't know however, if there is significant gain with other
more elegant solutions, provided you can't use svk at work.
if you expect that there may be conflicts with the modifs of other
people, it's good to prepare a branch either before you quit the office
or before importing the bzr changes.
2007/12/4, Matthew Hannigan <mlh@zip.com.au>:
> On Tue, Dec 04, 2007 at 04:53:52PM +0100, Michael Haggerty wrote:
> > Christian Convey wrote:
> > > I've got a repository that I'll sometimes not have access to. When
> > > I'm away from the repository, I'd still like to be able to track the
> > > local revisions I make to my code. [...]
> > >
> > > How do people work around this with SVN? (In case it matters, all
> > > computers involved are running Linux.)
> >
> > Another solution is quilt:
> >
> > http://www.suse.de/~agruen/quilt.pdf
> >
> > quilt is lighter weight than SVK, and excels at allowing you to go back
> > over old commits and refine them before committing them upstream.
> >
>
> Both bzr http://bazaar-vcs.org/ and git http://git.or.cz/ have
> svn modules that make it more or less easy to talk to svn repos.
>
> Watch out though - you may like them so much you might not want to
> go back to svn.
>
>
> Matt
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Dec 8 16:40:08 2007