Herbert Duerr wrote:
On 12.11.2013 16:48, janI wrote:
@herbert, if nobody objects will you reopen the ticket, or should I ?
I have reopened the JIRA issue and requested a read-only mirror for now.
And what would be the advantage for real contributors in having a
read-only GIT mirror? The complaints I've seen so far are mostly in the
other direction (i.e., committing or applying patches). I'm not talking
about generic advantages of GIT: everybody here can be assumed to have a
good working knowledge of both SVN and GIT. What concrete problems does
a read-only GIT mirror solve in our case?
I'm not at all against it, but I'd just like to make sure that a
read-only GIT mirror brings enough concrete advantages, since many GIT
niceties (local commits, proper attribution, quick application of
patches) are still left out or significantly limited with this approach.
By the way, you can find discussions about GIT everywhere at Apache,
there's even a Github account https://github.com/apache and lots of
suggestions like adopting the newly-released Apache Allura (Incubating)
GIT (and more) hosting environment. As far as I know, there have been
very significant updates in the GIT support at Apache in the last few
weeks and I hope that this is soon summarized in a blog post at
http://blogs.apache.org/infra/ or reflected in the documentation at
http://www.apache.org/dev/git.html . So this is a good moment to start
considering GIT again.
Regards,
Andrea.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
