I'm confused as to why you are mentioning branches?
I don't want my own branch to work on. I was to have my own private copy
of some of the work I do. For example I wrote something in my spare
time, brought it to work and checked it in. But now if I make a bugfix
then I have to copy it back home and check it in there as well. Stupid.
I'd like to make a bugfix and have both a copy at work and a copy at
home, separate repositories. The second one at home is private to me and
things I work on. It is not for anybody but myself to access. I just
don't want to have to duplicate work.
>> -----Original Message-----
>> From: Ryan Schmidt [mailto:firstname.lastname@example.org]
>> Sent: Monday, December 11, 2006 4:27 PM
>> To: Hari Sekhon
>> Cc: email@example.com
>> Subject: Re: Sharing files between repositories
>> On Dec 11, 2006, at 04:03, Hari Sekhon wrote:
>>> Ryan: Thanks for the link, svk looks interesting. Unfortunately this
>>> is not realistically an option if I would have to change the repo at
>>> work since more people than just myself use this and it just
>>> be possible to change repos (not to mention losing 15000 revisions
>>> which wouldn't go down well)
>> SVK is based on Subversion; I didn't think you'd need to
>> change the repository at all. But you'd have to ask the SVK
>> folks to make sure.
> Ryan is correct! With SVK, you "mirror" the Subversion repository,
> essentially giving you what you want - your own repository.
> I ask again, why not just use a branch?
Received on Tue Dec 12 11:50:59 2006