On Fri, 2014-05-16 at 15:01 -0700, James Bottomley wrote: > On Fri, 2014-05-16 at 15:38 +0200, Hannes Reinecke wrote: > > On 05/15/2014 07:26 AM, Christoph Hellwig wrote: > > > Hi James, > > > > > > we're past -rc5 and no SCSI patches have been collected for 3.16 yet, > > > despite a lot of patches including a lot of reviewed ones pending on the > > > list. > > > > > > I'd really love to get at least some testing for all the work that > > > sometimes has been pending for months in linux-next and would offer to > > > put together a tree of reviewed patches for linux-next. Is this fine > > > with you? > > > > > Seconded. Having a staging tree would make my life _so_ much easier. > > OK, I think we can do this easily. Send me your staging branches and > I'll pull them into a global staging branch and merge it with for-next > in linux-scsi ... this will ensure we don't get yelled at for duplicate > commits causing merge rejections in linux-next. Since staging will be > volatile and for the purposes of testing patches on upstream track, we > don't need signed tags or anything. Ping ... Git URL, anyone? I thought this was something you really wanted and an essential component to making your lives easier? Like I said, just the URL will work for a staging tree, I don't need signed tags or commit descriptions ... although if testing by next or Fengguang shows fatal problems, I'll drop the branch. James -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
