Readme mentions 4 steps but only 3 are explicitly mentioned about pasta HOT 5 CLOSED

And we can close this one.

from pasta.

You're right, I can also only count 3. Off by one. :-)

Uhm, other than that, step one only makes sense in PatchStack mode (PaStA is also able to compare repositories against each other). The Mbox support was an extension that was later added to PaStA.

from pasta.

Uhm, other than that, step one only makes sense in PatchStack mode (PaStA is also able to compare repositories against each other). The Mbox support was an extension that was later added to PaStA.

Took some time for me to figure that out by myself. Should probably document that for other users.
Also how do you generate the patch-stack-definition.dat files used in PatchStack mode?

PaStA is also able to compare repositories against each other

Do you mean compare revisions against each other here? What does comparing repositories mean exactly?

from pasta.

Hah... Good question!
That's a semi-automatic step at the moment.
There's a script, update-preemptrt.sh It downloads all new stacks, applies them on separate branches and creates a file called 'psd'. I'm then filling out missing entries in that file, and merge entries with the patch-stack-definition.dat. But no need to go into this direction.

This is the way how PaStA initially used to work. Support is still there, but we focused on mailing list analysis after a while. If you're interested why and what we did in the PreemptRT project, you can have a look here: https://arxiv.org/abs/1607.00905

from pasta.

This is the way how PaStA initially used to work. Support is still there, but we focused on mailing list analysis after a while.

Seems like I am missing a bit of historical context that's tripping me up.

If you're interested why and what we did in the PreemptRT project, you can have a look here: https://arxiv.org/abs/1607.00905

Will give it a read. Thanks!

from pasta.