Why not move web development as well as the code development into Git? +1 any Git.
Sent from my iPhone > On Mar 1, 2015, at 6:59 PM, Dennis E. Hamilton <dennis.hamil...@acm.org> > wrote: > > I'm going to add my +1 to this proposal. > > It occurred to me, when looking into the "old OOo SVN dumps" that Rob has, > that there may be many more downstream users that are on Git and that our > being on Git would facilitate accepting appropriately-offered pull requests > to the AOO repository. It seems this is a lower-friction way of sending > fixes upstream than going the patch creation and submission route. > > - Dennis > > -----Original Message----- > From: Jürgen Schmidt [mailto:jogischm...@gmail.com] > Sent: Tuesday, February 17, 2015 04:01 > To: dev@openoffice.apache.org > Subject: Re: [PROPOSAL] move repo to Git. > > [ ... ] > > If possible to get a git repo only it make sense. That means we don't > have to move any webpage related stuff into git. Just the pure code is > relevant her. > > +1 for a git repo > > Juergen > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
