[Libosinfo] [PATCH osinfo-db] dragonflybsd : Add DragonFlyBSD data
Pierre-Alain TORET
pierre-alain.toret at protonmail.com
Thu Jul 19 12:14:07 UTC 2018
On 19/07/2018 13:30, Fabiano Fidêncio wrote:
> On Thu, Jul 19, 2018 at 10:40 AM, Pierre-Alain TORET
> <pierre-alain.toret at protonmail.com> wrote:
>> On 19/07/2018 10:02, Fabiano Fidêncio wrote:
>>> On Thu, Jul 19, 2018 at 9:47 AM, Pierre-Alain TORET
>>> <pierre-alain.toret at protonmail.com> wrote:
>>>> Hello Fabiano,
>>>>
>>>> On 19/07/2018 07:59, Fabiano Fidêncio wrote:
>>>>> Pierre-Alain,
>>>>>
>>>>> On Wed, Jun 6, 2018 at 10:54 PM, Pierre-Alain TORET
>>>>> <pierre-alain.toret at protonmail.com> wrote:
>>>>>> Hello,
>>>>>>
>>>>>> [...]
>>>>>>
>>>>>> Signed-off-by: Pierre-Alain TORET <pierre-alain.toret at protonmail.com>
>>>>>
>>>>> For some reason I'm not able to apply your patches atop of git master.
>>>>> It may be some issue on my mail client breaking the patches lines in
>>>>> an weird way.
>>>>>
>>>>> Would you have those patches on a git repo that you could point me to?
>>>>> I'd like to review and have them merged sooner than later.
>>>>>
>>>>
>>>> Actually I cleaned my repos just 2 days ago, this is really bad luck.
>>>> I tried and can't apply the patch myself neither so it seems there's an
>>>> issue with what I sent.
>>>> I guess I will have to make a new patch by hand, but this will take a
>>>> little time, except if someone has a better solution.
>>>
>>> Okay. :-/
>>
>> Ah actually I found the .patch files generated at that time, so I
>> re-used them and pushed on my gitlab fork of the projects :
>> https://gitlab.com/daftaupe/libosinfo/tree/dfly
>
> This repo seems to be closed and I can't access it.
>
Sorry this repo was in private mode, and the other in public mode, I
don't why as I just forked both of them.
Anyway you should have access now.
>> https://gitlab.com/daftaupe/osinfo-db/tree/dfly/
>
> This one is fine!
>
>>
>> I added release 5.2.2 while at it :)
>>
>> Sorry for the noise.
>>>
>>> I'll go and prepare a release later Today with what we have merged and
>>> this series will be in the next one.
>>> Hopefully it's not a big problem for you.
>>>
Sorry, I didn't answer to that. It's totally fine.
>>>>
>>>>> Sorry for the long time taken for reviewing those.
>>>>>
>>>>
>>>> No problem.
>>>>
>>>> I'll seend a new one when it's ready.
>>>
>>> Thanks a lot!
>>>
>>>>
>>>>>> [...]
>>>>
>>>>
>>>
>>>
>>>
>>
>>
>
>
>
More information about the Libosinfo
mailing list