One suggestion - it seems that creating and deleting repos is a relatively cheap operation in gitorious, so how about creating individual cloned repositories for each specific feature or bug fix, and requesting the merge from the relevant repo. That would definitely keep things cleaner and easier to keep track of.
Cheers, Ciaran Adrian Lang wrote: > Dear laconica-dev, > > I think the current work flow with git repo clones and merge requests is > a great way to make the development process open for many people > (including irregular contributors like myself). Yet evan lately switched > to cherry-picking commits from the clones instead of completely merging > them into dev; I quite understand this since some of the clones > (including my own) hold a big amount of commits, with very different and > partly hard to review fixes. > > Unfortunately this leads to an unclear situation for those who requested > a merge (Which commits are merged already? Are there specific problems > with the other commits?) and those who are about to request their > changes to be applied to the upstream code base (How should I request > this? How should I request a cherry-pick of a concrete commit?). > > I encountered both of these situations: > - My commit > http://gitorious.org/projects/laconica/repos/adrianlang-clone/commits/1151b961 > is not applied to dev and I dont know why. > - I want my commit > http://gitorious.org/projects/laconica/repos/adrianlang-clone/commits/adcb889f > to be included in dev and I dont know whether I should create a new > merge request. > I think both commits are rather important to improve Laconicas OMB > compliance, but thats not really relevant. > > What do you think about these raised questions? How could we improve the > process for contributors and maintainers? > > Regards, > Adrian Lang / Codeispoetry _______________________________________________ Laconica-dev mailing list [email protected] http://mail.laconi.ca/mailman/listinfo/laconica-dev _______________________________________________ Laconica-dev mailing list [email protected] http://mail.laconi.ca/mailman/listinfo/laconica-dev
