Thanks Michael: it seems to work fine. Ill commit your change. Then we can discuss the bugs in the process (i see a few already, but so far they have nothing to do with whether committers use git or svn though)
On Sat, Jan 4, 2014 at 11:26 AM, Michael Della Bitta <michael.della.bi...@appinions.com> wrote: >> So from your perspective, this workflow can already work today. (do > you want to try it, for some trivial fix?) > > Just published a pull request. Let me know if that showed up. Ironically, > Github had a "ProTip" about using git merge --no-ff at the top. :) > > Michael Della Bitta > > Applications Developer > > o: +1 646 532 3062 | c: +1 917 477 7906 > > > appinions inc. > > “The Science of Influence Marketing” > > > 18 East 41st Street > > New York, NY 10017 > > t: @appinions | g+: plus.google.com/appinions > > w: appinions.com > > > On Fri, Jan 3, 2014 at 3:00 PM, Robert Muir <rcm...@gmail.com> wrote: >> >> On Fri, Jan 3, 2014 at 2:42 PM, Michael Della Bitta >> <michael.della.bi...@appinions.com> wrote: >> >> > That's a *lot* less compelling to me than the ability of creating my own >> > branch in a public arena, possibly collaborating with another person on >> > a >> > change, and then issuing a pull request. Plus, there's a public record >> > of >> > the work, and it's easy for another user to take up my changes without >> > having to find the patch in JIRA and run it themselves. >> > >> >> Also: if you fork https://github.com/apache/lucene-solr today, you can >> have this workflow, I think. From my understanding when you issue your >> pull request, it emails the list. >> >> So from your perspective, this workflow can already work today. (do >> you want to try it, for some trivial fix?) >> >> This discussion is more about what the committers are using (either >> svn or git)... even if we use git, i think the apache repository is >> only writable by committers, so you'd be in the same boat. >> >> --------------------------------------------------------------------- >> 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
