On Mon, Aug 08, 2011 at 06:10:58PM +0200, Arend van Spriel wrote: > On 08/08/2011 04:53 PM, Dan Carpenter wrote: > >On Mon, Aug 08, 2011 at 04:29:49PM +0200, Sedat Dilek wrote: > >>2. Using "staging/brcm80211" would also save some chars (and is more > >>common to me). > >No one would complain if the prefix were "staging/brcm80211" but > >actually the way Arend has it is prefered. > > > >git log --pretty=oneline --author=gregkh drivers/staging/ > > Nice. Learning something today about --author filter. > >>3. "PATCH v2" should be with a space? > >git am doesn't care. It strips everything out correctly. > > > >>4. Something like "for-3.1" would clearly indicate for which > >>kernel-release this mega-series is for (also "staging" could be > >>dropped as it is known where the driver is managed) > >> > >>$ git format-patch --signoff --cover-letter --subject-prefix="PATCH v2 > >>for-3.1" -82 (or whatever $FIRST..$LAST) > > I actually would think this all is for 3.2 as 3.1 has already been > merged hence 3.1-rc1 and only bug fixes are to be merged into 3.1. > > >Everything was explained in the cover letter, so I think it's ok. > > > >regards, > >dan carpenter > > Thanks. I leave it as it is unless Greg sees good reasons to change > any conventions here. No, as you sent it is fine with me. I'll start going through the huge backlog of staging patches this week, as the merge window just opened up a few hours ago. thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
