Context Around a year and a half ago, I’ve asked my former company for some time to work on an issue that was impacting the debugging capabilities in our project: gdbserver couldn’t debug multithreaded applications running on a PowerPC32 architecture. The connection to the gdbserver was broken and it couldn’t control the debug session anymore. Multiple people have already investigated this problem and I had a good starting point, but we still weren’t sure in which software component the issue lied: it could have been the toolchain, the gdbserver, the Linux kernel or the custom patches we applied on top of the kernel tree. We were quite far away from finding the root cause.
  • @MajorHavoc
    17•1 year ago

    I’m surprised there’s not more discussion of the git GitHub co-author feature here.

    A simple co-author line in the final commit sounds like an appropriate way to use the best final code while also giving due credit.

    • JackbyDevEnglish
      3•1 year ago

      I believe that is just a GitHub feature. Trailers are not some special field in the commit, just things at the end of the commit message. Sort of like an email signature. (Not a great example, I know.) My point is that the use of trailers will vary from project to project.

      • @MajorHavoc
        3•1 year ago

        Good point!

        It looks like GitLab doesn’t have Co-Author support yet, yet.

        At least - as part of the git history - co-author notes in commits can survive a migration away from GitHub.

        It’s not clear if the current GitHub implementation will be the long term accepted standard, of course.