On Sun, Aug 2, 2009 at 7:33 PM, Gerrit Voß<[email protected]> wrote:
>
> Hi,
>
> On Sun, 2009-08-02 at 13:00 -0500, Carsten Neumann wrote:
>>       Hello Allen,
>>
>> Allen Bierbaum wrote:
>> > What about using Mercurial (Hg) on google code instead?  I have heard
>> > that it has a much simpler interface so to most users it would look
>> > very similar to svn, but for those of us that may want to have
>> > distributed repositories we can still do it.  So basically use a model
>> > where the google hosted one is the master repository with
>> > user/organization specific distributed repositories pulling/pushing to
>> > that repository.
>> >
>> > Would this work for your needs?
>>
>> probably (well, for me at least), but so does the current setup with a
>> local git repo ;)
>> I don't think we have compelling reasons to change VCS, so we probably
>> should not add that work to the list :)
>
> Similar for me. git in combination with svn works fine for all my needs.
> I really don't need more. svn in this setting actually behaves like a
> linear git repository, you just use different commands to pull/push.
>
> And this is something I would like to keep, even if the master switches
> to hg.
>
> And the one thing that makes an 'official' git or hg repository
> interesting, providing a platform to publish individual developer trees
> from a single location is currently not available on google code.
>
> http://code.google.com/p/support/issues/detail?id=2563
>
> But at least it's priority is high so it might be resolved in a
> reasonable amount of time.
>
> Is there anything on your side that would be easier to handle with
> a distributed repository like git or hg ?

We currently us a vendor branch to try to keep a stable version of
OpenSG for our usage.  Git or Hg may assist in this by allowing us to
cherry pick some changes and leave out others, but this isn't a
critical need and truth be told, we probably don't understand all the
changes well enough to cherry pick accurately.

Just having an relatively stable and reliable trunk in svn would give
us everything we need. (ie. no new crashes or memory leaks :)

-Allen

>
> kind regards,
>  gerrit
>
>
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Opensg-core mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/opensg-core
>

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Opensg-core mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-core

Reply via email to