Florian Klaempfl wrote: >> >>> blocking of patches from merging >> it's called cherry-picking in git. > > No. It does not prevent that somebody pushes a merge.
If you don't like there changes you probably don't trust them to push to your repository. In that case, you pull from them (which would be my preferred choice). The developer can send you a pull request and you can accept or pick what you want. If the other developer did manage to push something you did not want, kill his access (as he clearly did not listen to you) and undo that specific commit on your side. The following URL shows 4 different ways of handling specific commits from somebody else. http://www.gitready.com/intermediate/2009/03/04/pick-out-individual-commits.html Regards, - Graeme - _______________________________________________________ fpGUI - a cross-platform GUI toolkit using Free Pascal http://opensoft.homeip.net/fpgui/ -- _______________________________________________ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
