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
Description
Stockroom's stockfile mechanism is not good enough for handling merges and merges conflicts. Since the
head.stockfile 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.