Thomas, As you could have found out by reading the exact same thread which comes up every time someone asks this question, no ASF project will be on git at any point in the forseeable future.
And no, most people I know of use git-svn. They do it "the old fashioned way", with multiple checkouts and downloaded patches. But Grant - I don't think the provenance of the code is much of a problem, you could certainly still have only "committers" have write access to the "master" git repo, right? It's not like the Linux source tree has any trouble keeping track of where stuff comes from, and they've got even more reason to make sure that their code is of reliable provenance than ours. It would just take a huge change of culture to get that kind of thinking in the Apache world, and so it's not going to happen until the majority of the committers have been primarily using git (or something like it - on other projects, for other reasons) for many years. -jake -jake On Sat, Apr 17, 2010 at 12:20 AM, Thomas Koch <[email protected]> wrote: > Hi, > > at least since august 2009 nobody has dared to ask this question, so let's > start a flamewar: > Don't you think, it's time for lucene and solr to switch to GIT? > > And now seriously: > I did the last packaging of SOLR 1.4 for Debian and I intend to continue > doing > so. Since I'm doing the packaging in GIT, I'm asking myself, whether I > should > base the packaging GIT repository on the SOLR repo found at git.apache.org > ? > However if the one from git.a.o is not stable and may crash at any given > time, > this would not be a good idea. > And the best thing for those packagers like me would be of course, if the > GIT > repo would be the official one. > > And I wonder, if there are really people using SVN and downloading douzens > of > patch files from jira? Isn't it, that everybody already uses git-svn? > > Best regards, > > Thomas Koch, http://www.koch.ro > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
