On Thu, 07 Dec 2006, Len Brown wrote: > Henrique, > FYI, A pull of this branch will take everything included underneath it. > In this case, it will take all the contents of acpi-test that this branch is built upon. > > That is fine for testing, but it isn't a path to upstream b/c > not everything in acpi-test is going to get sent up to Linus at the same time as ibm-acpi. I was operating under the false idea that the flow should be ibm-acpi-devel -> acpi-test -> linus. > For this batch, I'll just re-parent the series, or re-commit the e-mail patches. Thanks. > But in the future, if you base your patches directly against some snapshot of Linus' tree > and don't include anything else besides your changes, then I can pull it directly. > Of course you can do both by checking your changes in on a branch off of Linus' > baseline and then merging onto your mirror of acpi-test. In that event I'd > pull from your branch based on Linus' mirror. Will do. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ ibm-acpi-devel mailing list ibm-acpi-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/ibm-acpi-devel
