Audio and transcript of a discussion of the goals and intent of the Git Patch Stack project.

  • tatterdemalion@programming.dev
    link
    fedilink
    arrow-up
    5
    ·
    edit-2
    1 year ago

    OK but what is “Git Patch Stacks”? It seems like I’m missing something fundamental that was never actually explained in this post.

    EDIT: Oh hey I found it after reading a different blog post on that site: https://github.com/uptech/git-ps-rs

    The post is also super rambling in the middle section.

    I have to assume that this is something similar to Mercurial’s MQ plugin or Stacked Git (stgit), which allow you to manage revisions as a stack of diffs.

    I personally enjoy using stgit, and it fits just fine into the world of feature branches and PRs.

    This part scared me:

    In a Stacked Branch workflow, you are creating branches for each of your atomic commits, and then you’re defining the relationships between those branches so it can formally store a directed acyclic graph of those relationships.

    Why do you want to make a separate branch for every commit? That sounds like a nightmare, and it’s definitely not the intended workflow for git.