On Mon, Nov 9, 2009 at 10:25 PM, Loui Chang <louipc.ist@gmail.com> wrote:
Ah. I guess I should pay more attention on this mailing list. Is there any document describing who's branches/repos I should check before submitting patches? That could be helpful. I've just been following the main repo.
I think it happened several times people writing patches on top of the stable release, for something that was fixed in git master. But for something not in git master but in someone branch, it is quite rare. That's because simple bugfixes are typically the first ones to be merged to master and that's done quickly. The situation right now for makepkg is a bit special though. The patches are frozen because we want to merge the big [[ (( test patch first. So Allan is accumulating patches in his working branch : http://projects.archlinux.org/users/allan/pacman.git/log/?h=working But just for your information, there are only 4 git tree : Allan : http://projects.archlinux.org/users/allan/pacman.git/ me : http://code.toofishes.net/cgit/xavier/pacman.git/ dan : http://code.toofishes.net/cgit/dan/pacman.git/ nagy : http://repo.or.cz/w/pacman-ng.git And dan merges stuff from these 4 tree to the primary one : http://projects.archlinux.org/pacman.git/