Many patches (even big ones) attached to JIRA issues are good as *can be*good a pull request and IMO a patch is, in many cases, better than a pull request... Accept a path was never a problem when the patch is good and do something useful... the prove is there in 5 years of history and less then 300 opened issues (numbers does not lie).
Btw it seems that now you have what you was looking for, let go to work. On Mon, Sep 12, 2011 at 12:51 PM, Ramon Smits <[email protected]> wrote: > >> -No it does not annoy me. When the decision is took then is took. What may >> annoy me is, as most, the change of the focus because when the focus >> changes, the number of opened issues increases day by day even when the >> sources are hosted in github. btw there is no problem because now the >> sources are DISTRIBUTED. >> >> Defines yourself as "not a committer" means that you have >> not completely clear the meaning of the DCVS. >> > > With not a committer I ment not somebody who has the rights to commit > changes in any of the official branches. This is unchanged when using a DCVS > as there is just one official repository. I do however contributed some > issues with code in Jira and this process is now easier as I could now just > refer to my own branch. > > Having distributed sources will not remove problems. The sources have > always been available thus be maintanable by others but accepting their > patches is a PITA for non DCVS systems. That the primary reasons why > NHibernate is now hosted in a DCVS is that git is just much faster then > subversion when updating and that importing contributions is easier and not > because it is now able for developers to commit disconnected. > > -- > Ramon > -- Fabio Maulo
