From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-pv0-f174.google.com ([74.125.83.174]:47622 "EHLO mail-pv0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752775Ab1GAAGH (ORCPT ); Thu, 30 Jun 2011 20:06:07 -0400 Received: by pvg12 with SMTP id 12so2061711pvg.19 for ; Thu, 30 Jun 2011 17:06:07 -0700 (PDT) Date: Fri, 1 Jul 2011 03:05:26 +0300 From: Dan Carpenter To: Henry Ptasinski Cc: =?utf-8?B?UmFmYcWCIE1pxYJlY2tp?= , "gregkh@suse.de" , "linux-wireless@vger.kernel.org" , "devel@linuxdriverproject.org" Subject: Re: [PATCH 000/119] staging: brcm80211: more code cleanup and bug fixed Message-ID: <20110701000526.GD2544@shale.localdomain> (sfid-20110701_020619_484230_C02A32B3) References: <1309391303-22741-1-git-send-email-frankyl@broadcom.com> <4E0CB587.3000209@broadcom.com> <20110630183258.GB2544@shale.localdomain> <4E0CED43.50305@broadcom.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <4E0CED43.50305@broadcom.com> Sender: linux-wireless-owner@vger.kernel.org List-ID: On Thu, Jun 30, 2011 at 02:40:19PM -0700, Henry Ptasinski wrote: > So there are two suggestions here: > > 1. post patches in smaller bunches, and include dependency info in > the 0/X patch. Presumably, if one of the dependencies is dropped, > then people will know to drop this series as well, and we would have > to repost everything that was dropped once we fix the identified > issues. > > 2. maintain a public git tree that people can pull from. If we do > (1), is this needed and/or still useful? Yes. Patches hiding in git trees never get reviewed. They just pile up until there too many to review. > Do community folks that > want to contribute changes send them to us or Greg/John/whoever is > upstream? Pros/cons? That stuff is between you and Greg. The rest of us don't care. But what I'm saying is don't delay sending these patches because you're not sure if the other patches were going to go in or not. It's not an unpredictable thing. Everyone is supposed to CC you along with Greg, linux-wireless and driver-devel. You're the maintainer. If you ack a patch or nack it, then 99% of the time Greg is going to go along with your decision. It's not like Greg is going to complain if you start recording which patches have to go in next and deal with any merge conflicts... regards, dan carpenter