Hi,
I have an open-source project an begin seriously to wonder if I
should not migrate to Google's Project Hosting. Managing my own
server is time- and money-consuming, and yet I do not have all
the nice features you provide, like the issue tracking system
with links to the repository and
On Wed, Mar 17, 2010 at 10:03 AM, Florent Georges fgeor...@gmail.comwrote:
Hi,
I have an open-source project an begin seriously to wonder if I
should not migrate to Google's Project Hosting. Managing my own
server is time- and money-consuming, and yet I do not have all
the nice features
On 17 March 2010 16:15, Nathaniel Manista wrote:
We do, however, support multiple project repositories for projects that use
the Mercurial version control system, and if you had any inclination to
switch to Mercurial you could use a conversion tool (such as HgSubversion)
to convert your
Another option (for now) is to combine your 4 repositories into one
repository by using svnadmin dump and load. Then svnsync the final
result to googlecode.
--
You received this message because you are subscribed to the Google Groups
Project Hosting on Google Code group.
To post to this
Another option (for now) is to combine your 4 repositories into one
repository by using svnadmin dump and load. Then svnsync the final
result to googlecode.
But, if you did want to keep them separate yet still 'share' some code, you
could always 'link' the repositories using the
On 17 March 2010 16:55, Ben Collins-Sussman wrote:
Another option (for now) is to combine your 4 repositories into one
repository by using svnadmin dump and load. Then svnsync the final
result to googlecode.
Interesting. But then, how are handled revisions? Revision say,
12, is
On 17 March 2010 17:06, Darren Pearce-Lazard wrote:
But, if you did want to keep them separate yet still 'share' some code, you
could always 'link' the repositories using the svn:externals property. Note
that this is purely a Subversion feature so will not mean that issue lists,
etc, will be
But, if you did want to keep them separate yet still 'share' some code,
you
could always 'link' the repositories using the svn:externals property.
Note
that this is purely a Subversion feature so will not mean that issue
lists,
etc, will be amalgamated.
Thanks. But the goal is to
On 17 March 2010 17:23, Darren Pearce-Lazard wrote:
It is independent of the backup strategy. :-) I was assuming that your four
projects would be hosted separately on Google Code Hosting and you could
'cross-link' between them.
It was just an alternative suggestion to Ben's.
There's
It is independent of the backup strategy. :-) I was assuming that your
four
projects would be hosted separately on Google Code Hosting and you could
'cross-link' between them.
It was just an alternative suggestion to Ben's.
There's discussion of all this in the Subversion
book:
10 matches
Mail list logo
