On 12.11.2013 20:08, Andrea Pescetti wrote:
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?
A git mirror is needed as a first step also when we do the full switch.
The read-only mirror can start immediately without any disruption and we
can switch to full git at a convenient time.
And there are other goodies too:
- A R/O mirror gives a reference point. As individual git-svn clones of
the asf-repo are often different because of "svn propedit" having an
official git-mirror would be nice.
- It gives time to rewrite our buildbot recipes.
- It gives time to rewrite our repo2bz service.
- It gives time to rewrite the svnlog2info script.
- It gives time to rewrite our building guides.
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.
Local branches, local commits, interactive rebasing, etc. are all
available directly.
When every service we like now has been converted to run with the
git-mirror we can switch to full git conventiently.
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.
Absolutely. I'm a big git fan and used it in my daily work since 2005!
Then I ran git in my CVS checkout, later in the SVN checkout, then the
git-svn bridge, then the hg-git bridge and finally the git-svn bridge again.
Even when tracking other projects (e.g. to see when boost fixed a
particular problem) I always look for its git-mirror first. Thats why I
know how powerful even a read-only git-mirror is.
Herbert
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
