Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Readme mentions 4 steps but only 3 are explicitly mentioned #43

Closed
rsarky opened this issue Mar 17, 2020 · 5 comments
Closed

Readme mentions 4 steps but only 3 are explicitly mentioned #43

rsarky opened this issue Mar 17, 2020 · 5 comments

Comments

@rsarky
Copy link
Contributor

rsarky commented Mar 17, 2020

This is probably a minor documentation quirk
According to the README: The detection phase is split in four steps:
But there are only 3 explicitly mentioned steps.

@rralf
Copy link
Member

rralf commented Mar 17, 2020

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.

@rsarky
Copy link
Contributor Author

rsarky commented Mar 17, 2020

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?

@rralf
Copy link
Member

rralf commented Mar 17, 2020

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

@rsarky
Copy link
Contributor Author

rsarky commented Mar 17, 2020

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!

@rralf
Copy link
Member

rralf commented Apr 26, 2020

And we can close this one.

@rralf rralf closed this as completed Apr 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants