+1 David and Mark I also like Lajos have - very sadly - not contributed as much as I'd want to Lucene, but having followed this thread with interest for a while, I hope my contribution is well received.
I do sympathize with all the "problems" which have been highlighted about Git as I've had the same impression 3 years ago when all our projects (Hibernate) where moved to Git, and I was the skeptical one back then. I have suffered from it for a couple of weeks, while I was pointlessly trying to map my previous SVN workflow on Git.. until I realized that that was the main crux of my pain with it. I really do have to admit I was just stubborn and grown up in bad habits, I'm extremely happy we moved now.. and yes - no offence - but from an outsider you all look like carving code on a stone wall with stone axes. Sparing you all the details of what I did wrong and how exactly it should be used the point is really a huge flexibility and a better model for the problem it solves. On this thread I've seen several "problems" being pointed out about git, but while I'd be happy to chat about each single one, for the sake of brevity my impression is just confusion by people who are trying to use it as it was an alias to svn. To put it boldly you're missing the point :-) If you need details, feel free to ask here or contact me on IRC: I'm afraid my email is too long already. Would be good to see some "negative points" from someone who actually used it for a significant time. From my part for example I don't like the complexity of handling merges; but then again we also use fast-forward only; considering that, maybe I've never actually understood how a merge should be done - as I've never practiced it. Please take it as an example of how you don't need to learn all its details and still get huge benefits from it: in 47 releases, for 3 years long, ~100 contributors have been happily collaborating, we developed a workflow which suites us best and never ever needed to do a merge. And yes I confirm it feels very odd for an occasional contributor that you guys still work by attaching patch files to JIRA. - Sanne On 8 January 2014 00:45, David Smiley (@MITRE.org) <dsmi...@mitre.org> wrote: > +1, Mark. > > Git isn't perfect; I sympathize with the annoyances pointed out by Rob et. > all. But I think we would be better off for it -- a net win considering the > upsides. In the end I'd love to track changes via branches (which includes > forks people make to add changes), not with attaching patch files to an > issue tracker. The way we do things here sucks for collaboration and it's a > higher bar for people to get involved than it can and should be. > > ~ David > > > Mark Miller-3 wrote >> I don’t really buy the fad argument, but as I’ve said, I’m willing to wait >> a little longer for others to catch on. I try and follow the stats and >> reports and articles on this pretty closely. >> >> As I mentioned early in the thread, by all appearances, the shift from SVN >> to GIT looks much like the shift from CVS to SVN. This was not a fad >> change, nor is the next mass movement likely to be. >> >> Just like no one starts a project on CVS anymore, we are almost already to >> the point where new projects start exclusive on GIT - especially open >> source. >> >> I’m happy to sit back and watch the trend continue though. The number of >> GIT users in the committee and among the committers only grows every time >> the discussion comes up. >> >> If this was 2009, 2010, 2011 … who knows, perhaps I would buy some fad >> argument. But it just doesn’t jive in 2014. >> >> - Mark > > > > > > ----- > Author: http://www.packtpub.com/apache-solr-3-enterprise-search-server/book > -- > View this message in context: > http://lucene.472066.n3.nabble.com/The-Old-Git-Discussion-tp4109193p4110109.html > Sent from the Lucene - Java Developer mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
