Adding Zenon. He also has to do this. Please wait a few hours before updating and working on the patch. I am still merging GCI tasks. :)
And make sure we merged everything. You guys wrote a LOT of code. --joel On Mon, Dec 10, 2018 at 12:48 PM Shashvat Jain <shashvatjain2...@gmail.com> wrote: > that will take some time :) > the number of methods for which tests are produces are around 300 , i > suppose > any other shortcut , like we can make python scripts , like Gedare and > Joel did to generate tasks . > > Shashvat > > On Tue, Dec 11, 2018 at 12:12 AM Marçal <mcomajoanc...@gmail.com> wrote: > >> I think you just have to clone the rtems repo and search for the files >> you wrote and licensed. Then replace the license there is with the one on >> the link. >> >> Marçal (Sal) >> >> On Mon, Dec 10, 2018 at 7:40 PM Shashvat Jain <shashvatjain2...@gmail.com> >> wrote: >> >>> How will we edit all the test files to have the new license paragraph ? >>> >>> On Tue, Dec 11, 2018 at 12:05 AM Shashvat Jain < >>> shashvatjain2...@gmail.com> wrote: >>> >>>> yes sir , the psxtmtests also had the license paragraph , same as that >>>> of the compliace tests >>>> >>>> On Tue, Dec 11, 2018 at 12:01 AM Joel Sherrill <j...@rtems.org> wrote: >>>> >>>>> >>>>> >>>>> On Mon, Dec 10, 2018 at 12:21 PM Marçal <mcomajoanc...@gmail.com> >>>>> wrote: >>>>> >>>>>> Hi, >>>>>> I think we all have used that license because in the task >>>>>> instructions in the wiki ( >>>>>> https://devel.rtems.org/wiki/GCI/Coding/AddPOSIXMethodSignatureComplianceTests) >>>>>> says so. Do I change the wiki to the new license? >>>>>> >>>>> >>>>> Yes. >>>>> >>>>> And are the psxtmtests templates and tests the short license or the >>>>> BSD-2? They may also be impacted. >>>>> >>>>> Marçal (Sal) >>>>>> >>>>>> On Mon, Dec 10, 2018 at 7:13 PM Joel Sherrill <j...@rtems.org> wrote: >>>>>> >>>>>>> Hi everyone, >>>>>>> >>>>>>> I think I have cc'ed all of the GCI students who submitted code to >>>>>>> psxhdrs. >>>>>>> >>>>>>> Sebastian has asked that these files have 2 paragraph BSD which is >>>>>>> quite >>>>>>> similar to this one and makes the license consistent with other >>>>>>> files. >>>>>>> >>>>>>> https://git.rtems.org/rtems/tree/LICENSE.BSD-2-Clause >>>>>>> >>>>>>> I am in the process of merging the last GCI tasks in this category. >>>>>>> Please submit >>>>>>> a patch for all the files you wrote. >>>>>>> >>>>>>> Sebastian.. if I missed anyone, please reply and bring them in. Also >>>>>>> just help >>>>>>> get this resolved. >>>>>>> >>>>>>> Thanks. >>>>>>> >>>>>>> --joel >>>>>>> >>>>>>> On Mon, Dec 10, 2018 at 8:16 AM Sebastian Huber < >>>>>>> sebastian.hu...@embedded-brains.de> wrote: >>>>>>> >>>>>>>> On 09/12/2018 22:41, Marçal Comajoan Cara wrote: >>>>>>>> > + * Permission to use, copy, modify, and/or distribute this >>>>>>>> software >>>>>>>> > + * for any purpose with or without fee is hereby granted. >>>>>>>> > + * >>>>>>>> > + * THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL >>>>>>>> > + * WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED >>>>>>>> > + * WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL >>>>>>>> THE AUTHOR >>>>>>>> > + * BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR >>>>>>>> CONSEQUENTIAL DAMAGES >>>>>>>> > + * OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA >>>>>>>> OR PROFITS, >>>>>>>> > + * WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER >>>>>>>> TORTIOUS ACTION, >>>>>>>> > + * ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE >>>>>>>> OF THIS SOFTWARE. >>>>>>>> >>>>>>>> Would it be possible to change this to BSD-2-Clause? New files >>>>>>>> written >>>>>>>> specifically for RTEMS should have the standard project license and >>>>>>>> this >>>>>>>> is BSD-2-Clause from my point of view. >>>>>>>> >>>>>>>> -- >>>>>>>> Sebastian Huber, embedded brains GmbH >>>>>>>> >>>>>>>> Address : Dornierstr. 4, D-82178 Puchheim, Germany >>>>>>>> Phone : +49 89 189 47 41-16 >>>>>>>> Fax : +49 89 189 47 41-09 >>>>>>>> E-Mail : sebastian.hu...@embedded-brains.de >>>>>>>> PGP : Public key available on request. >>>>>>>> >>>>>>>> Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des >>>>>>>> EHUG. >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> devel mailing list >>>>>>>> devel@rtems.org >>>>>>>> http://lists.rtems.org/mailman/listinfo/devel >>>>>>> >>>>>>>
_______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
