Indeed, I'm a bit concerned that moving to subversion will make us
suffer from the 'good enough' syndrome. But I can clearly live with
that, if we agree that it's an interim solution (and given that svn
tooling for CWS is almost done - if we need to invest half a year to
have that running, we co
Martin Hollmichel <[EMAIL PROTECTED]> writes:
> A switch to DSCM is the bigger and a promising step: enhancements of
> our development model and style look possible...
>
Right - generally, a distributed approach fits the multi-tier,
decentralised world of OOo much better. Besides that, having the
Hi,
I had a lot of interesting discussion about various distributed SCM and
subversion in the meantime. For me it looks the discussion and evalution
of distributed SCM needs some more time than just a month because the
use of such a system also can improve or at least change our development
p
Jan Holesovsky wrote:
Hi Martin,
On Tuesday 24 April 2007 15:48, Martin Hollmichel wrote:
Some of the clones might be public, eg. ooo-build.
if people agree on a push back, only some of the clones needs to be
public, if this should be a pull back public access gets a problem.
so right now it
Hi Martin,
On Tuesday 24 April 2007 15:48, Martin Hollmichel wrote:
> > Some of the clones might be public, eg. ooo-build.
>
> if people agree on a push back, only some of the clones needs to be
> public, if this should be a pull back public access gets a problem.
>
> so right now it is no problem
Some of the clones might be public, eg. ooo-build.
if people agree on a push back, only some of the clones needs to be
public, if this should be a pull back public access gets a problem.
so right now it is no problem to access a cws which has not been
integrated yet and can e.g. do somethin
Hi Eric,
On Tuesday 24 April 2007 13:59, eric b wrote:
> Le 24 avr. 07 à 12:45, Jan Holesovsky a écrit :
> > The workflow I think is the most reasonable for OOo is the following:
> >
> > - up-stream has one head branch, 'master'
> >
> > - every other clone (StarOffice, ooo-build, MacOSX port, ...
Hi Jan,
Le 24 avr. 07 à 12:45, Jan Holesovsky a écrit :
The workflow I think is the most reasonable for OOo is the following:
- up-stream has one head branch, 'master'
- every other clone (StarOffice, ooo-build, MacOSX port, ...) have
2 head
branches, 'master' and 'origin'
Sorry, I don'
Hi Martin,
On Tuesday 24 April 2007 12:14, Martin Hollmichel wrote:
> > Should I enable http:// access to go-oo.org/git?
>
> this might ease things a bit,
OK, I'll try to ;-)
> but nonetheless if I want to give you
> access to my repository, I need to set up a repository which can be
> access
Thorsten Behrens wrote:
Jan Holesovsky <[EMAIL PROTECTED]> writes:
Should I enable http:// access to go-oo.org/git?
Dunno what went wrong for Martin - I was able to clone your repo from
within Sun.
which platform did you use, I was trying on Windows,
Martin
---
Jan Holesovsky wrote:
Hi Martin,
On Tuesday 24 April 2007 11:12, Rene Engelhard wrote:
I wondered then at all if a distributed SCM makes sense at all if many
developers are located in corporate networks, so access to distributed
repositories might be difficult or need extra infrastructure. Are
Jan Holesovsky <[EMAIL PROTECTED]> writes:
> Should I enable http:// access to go-oo.org/git?
>
Dunno what went wrong for Martin - I was able to clone your repo from
within Sun.
Cheers,
-- Thorsten
-
To unsubscribe, e-mail: [E
Hi Martin,
On Tuesday 24 April 2007 11:12, Rene Engelhard wrote:
> > I wondered then at all if a distributed SCM makes sense at all if many
> > developers are located in corporate networks, so access to distributed
> > repositories might be difficult or need extra infrastructure. Are there
>
> De
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Martin Hollmichel wrote:
> I just stumbled about how to use git in our corporate network (tried
> freecap on Windows) and failed.
Just out of curiosity: how?
> I wondered then at all if a distributed SCM makes sense at all if many
> developers
Hi,
I just stumbled about how to use git in our corporate network (tried
freecap on Windows) and failed.
I wondered then at all if a distributed SCM makes sense at all if many
developers are located in corporate networks, so access to distributed
repositories might be difficult or need extra i
15 matches
Mail list logo
