This message was deleted.

I would stack the change onto the branch which the commit has been merged into!

Ah to be specific, my goal is to keep track of commit dependencies over time. I found this really useful at FB for code archive purposes. i.e. let’s say i have a stack of commits

[1/n][feature] commit msg
[2/n][feature] another commit msg
[3/n][feature] one more commit msg

if I merge 1 and 2 before submitting 3, there’s no way (I think) to indicate in the graphite dep graph that commit 3 depends on 2.