Highlights from Git 2.48
github.blog
The open source Git project just released Git 2.48. Here is GitHub's look at some of the most interesting features and changes introduced since last time.
  • @uranibaba
    16•16 days ago
    • When “git fetch $remote” notices that refs/remotes/$remote/HEAD is missing and discovers what branch the other side points with its HEAD, refs/remotes/$remote/HEAD is updated to point to it.

    That is nice.

    • @[email protected]
      16•15 days ago

      Yep, whenever they fix a bug it’s added in a new flag that nobody knows about.

      git --enable-sane-behaviour
    • kbal
      7•15 days ago

      As a casual git user I imagine the process normally goes something like this:

      1. Development happens.
      2. New feature makes it into the release version of git.
      3. New version makes it into the various linux distro repositories.
      4. People who run big git repos install the update.
      5. Serious nerds hear about it and use the feature.
      6. Many years pass.
      7. I learn about it, if it’s widely used enough.
      • kusEnglish
        1•15 days ago

        The big change in my opinion is we don’t need to tell newcomers about git checkout at all. Git switch --create is much better.

  • @[email protected]
    7•15 days ago

    Git has four build systems?? Meson seems overkill if you already have CMake too. The only thing it really adds is that it’s nicer to write (CMake is somewhere between Bash and PHP in sanity), but if you have to write CMake anyway…

    • @[email protected]
      2•14 days ago

      The liquor store presumably? Just submitting patches is a simple 12 step process. I can’t imagine the development and review process is any easier.

      I have implemented a Git client from scratch which involved quite a bit of reading the Git source code. It’s not bad code but it’s definitely the sort of code that would break in all sorts of unexpected ways if you changed something. I wouldn’t volunteer my time their tbh.