8 Matching Annotations
  1. Apr 2024
    1. versión parche

      Esto Indica a una Versión de Correciones.

      Se conoce como Patch y son correcciones que solucionan problemas sin cambiar la funcionalidad de un software, esta funcionalidad es pensada en que no se afecte para que los usuarios no tengan problemas mayores en la interaccipon con la API.

  2. May 2023
  3. Mar 2023
  4. Aug 2022
    1. Every 60 seconds the equivalent of a lorry-load of plastic enters the global ocean. Where does it end up? Right now, researchers simply don’t know. But in a bid to help find out, an ESA-led project developed floating transmitters whose passage can be tracked over time, helping in turn to guide a sophisticated software model of marine plastic litter accumulation.

      Huh? The plastic ends up in the Garbage Patches - https://en.wikipedia.org/wiki/Great_Pacific_garbage_patch

      This is a surprising and disappointing oversight by ESA.

  5. Jun 2022
    1. He's also the co-founder of the hyperlocal community site outside.in.

      It no longer resolves, but outside.in sounds like the sort of project that fits into the sort of space similar to Darius Kazemi's Run Your Own Social.

      Archive.org makes it look like a hyperlocal space done at larger scale though... perhaps in a shape more similar to Patch? https://web.archive.org/web/20090618030413/http://outside.in/

  6. Feb 2019
  7. Feb 2018
    1. its own branch

      The patch branch should start at a common ancestor of all the target branches. Since the broken code is in all the target branches, it must be in at least one of their common ancestors.

      If we don't start from a common ancestor and merge the patch into all the target branches, at least one of the target branches will get some extra change along with the patch.