Skip to content

Merge & merge conflicts #10

Description

@hhsecond

Description

Stockroom's stockfile mechanism is not good enough for handling merges and merges conflicts. Since the head.stock file consists of only one line and that is that key to managing the stock read head, it's important to make it escape merge conflicts if there is no conflict in hangar internally. A thought suggested by @rlizzo is documenting here for reference.

                  (master)
    a ---- b1 ---- c1 
    \---b2 
     \  (dev)
     \-------b3
            (test)
    head.stock of master
    -----------------
    master c1
    head.stock of dev
    ---------------
    master a
    dev b2
    head.stock of test
    -----------------
    master a
    test b3
               (master)
    a ---- b1 ---- c1 
    \---b2 ------c2 (dev)
     \          /
      \-------b3
            (test)
    head.stock of master
    -----------------
    master c1
    head.stock of dev
    ---------------
    master a
    dev c2
    test b3
    head.stock of test
    -----------------
    master a
    test b3
                         (master)
    a ---- b1 ---- c1 ----- d
    |           (dev)      /
    \---b2 ------c2 ------/
     \          /
      \-------b3
            (test)
    head.stock of master
    -----------------
    master d
    dev c2
    test b3
    head.stock of dev
    ---------------
    master a
    dev c2
    test b3
    head.stock of test
    -----------------
    master a
    test b3

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions