On Mon, 2009-03-23 at 12:05 -0700, Vasu Dev wrote: > The entire patch series's code change is same as it was in its previous > submit at http://www.open-fcoe.org/pipermail/devel/2009-March/002037.html, > so no net code change since last submit. > > The fc_transport_fcoe.o in drivers/scsi/fcoe/Makefile was supposed to be > removed in patch 1/8 but perhaps I missed refreshing this change in > patch 1/8 and moved to next patch, so this change ended up in next patch > 2/8 in last submitted series and broke that patch 1/8. > > So in this series effectively change is to only patch 1/8 and rest of the > patches from last submit will also apply as-is on modified 1/8, however > I'm resending entire series as per Rob's request since as per Rob this > will help him collecting all changes from one series. > > However I'd prefer submitting only patch 1/8 to linux-scsi to avoid > resend of other same 7 patches from last submit. > I just asked JamesB and he's fine with sending just the updated patch. Now that I know that and looking forward- In this case where the patches were already submitted to linux-scsi I think it makes sense to just send me the one patch. However, if the patches haven't been sent to linux-scsi I would prefer whole sets with the patch change called out in the covermail.
I think it's error prone if I have to pull patches from mails on different dates. Basically, we run the risk that I make a mistake and pull the wrong patches. If the developer sends the whole set then there is no question, I just grab the latest set and I'm confident that it's what the developer intends me to push to linux-scsi. _______________________________________________ devel mailing list [email protected] http://www.open-fcoe.org/mailman/listinfo/devel
