axiom-developer
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Axiom-developer] RE: Google Repos


From: Gabriel Dos Reis
Subject: Re: [Axiom-developer] RE: Google Repos
Date: 13 Oct 2006 06:58:50 +0200

"Alfredo Portes" <address@hidden> writes:

| On 13 Oct 2006 05:54:44 +0200, Gabriel Dos Reis
| <address@hidden> wrote:
| > "Bill Page" <address@hidden> writes:
| >
| > [...]
| >
| > | SVK smerge seems like a good option. And it can be used in both
| > | directions if we decide we also want to merge changes at the Google
| > | repostiory back to the repository on SourceForge.
| >
| > Hey, if you decide two-way checking please do let me know so that I
| > know what I'm doing.  I'm pretty sure I'll confuse people and confuse
| > myself, which probably is why I would prefer "one master" repo, and
| > others act as mirror.
| 
| I think the idea of a master repo and mirrors is good. The question is
| which one should be the master repo???

Currently, SF is the master.

However, as I understand it key Axiom developers are having trouble
checking out from that repo, and probably checking in.  I, personally,
don't experience any _check-in_ problem, nor any _update_.  But I did
experience the checkout (not update, but checkout of entire branches)
problem using bare SVN from SF's own machines and some of the machines
I have at work.  I know my students reported several checkout
failures, so I end up putting the tarball on my web site. 

I use SVK for work, so I can convince it to relocate the repo assuming
Google's and SF's are in perfect sync.  But, of course the truly
egocentric way for me to go would be to suggest SF :-)
I'm not familiar with Google's setting.  What I do appreciate about SF
is the ability to have an admin shell, which truly is handy.  That is
my real argument for making SF repo the master.  I don't see how that
solves Tim's issue.  Now, I'm starting seeing the value of the master
repo being at axiom-developer.org ;-)

-- Gaby




reply via email to

[Prev in Thread] Current Thread [Next in Thread]