On 12 November 2013 16:57, Jürgen Schmidt <jogischm...@gmail.com> wrote:

> On 11/12/13 4:48 PM, janI wrote:
> > Hi.
> >
> > based on the discussion in thread "XML files are binary" and herberts
> > comments I had a chat with jfarrell (the infra git specialist).
> >
> > We can have a GIT Read/Only mirror very easy (standard)
> >
> > We cannot have a GIT Read/write mirror (restriction from infra)
> >
> > We can switch completely to GIT (which I for one would be against).
>
> can you share your thoughts against a complete switch with us. I am at
> least interested to learn more about others opinion.
>

of course.

I think there are still plenty of svn users out there, and switching
completely away from svn, would be a larger change for them.

At the moment (but this might just be me), branches in GIT works real bad
with our current build system. I have f.x. 3 branches and trunk, all being
build more or less daily. I tried with GIT, where branch switching is
supposed to be very simple. The branch switch itself is simple, but I
always needed a complete build --all, because the GIT do (of course not)
preserve the different unxlngx6.pro dirs.



>
> We talk here about "trunk" our real code repo only. Everything else can
> continue to be in svn.
>

That would be a problem, how will you do merge back ? The merge facility in
both directions is very important.

If we switch to git, svn will be a ReadOnly mirror and we cannot do merge
etc. in svn.

rgds
jan I.


>
> Juergen
>
> >
> > I recommend to reopen ticket 5590 with a comment asking for a read/only
> > mirror. Jfarrell is right now (this week) working through git issues, so
> if
> > we can reopen the ticket fast, I can help jfarrell make this happen fast.
> >
> > @herbert, if nobody objects will you reopen the ticket, or should I ?
> >
> > rgds
> > jan I.
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>

Reply via email to