Skip to content

Repository Cleanup (Persisting Issue) #173

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

Open
NicolasDenoyelle opened this issue Apr 22, 2021 · 2 comments
Open

Repository Cleanup (Persisting Issue) #173

NicolasDenoyelle opened this issue Apr 22, 2021 · 2 comments

Comments

@NicolasDenoyelle
Copy link

Comments under this issue list several cleanup actions to take and their motivations.

@perarnau
Copy link
Contributor

Since we have a full backup on xgitlab, I'm going through the branch list and deleting stuff that will never get merged, or was forgotten:

  • CI_cuda: leftover cuda test on gitlab, we went a different way
  • accelerate-ci: leftover nix config for gitlab ci. Was merged in some way but not deleted.
  • checkpatch: unsuccessful attempt at -Wall -Werror, ended up in a different direction later.
  • noarena: ended up with a different version merged
  • sparse_layout: empty

The rest of the stale branches are more difficult to deal with, there's a good amount of benchmarks and other code that we might want to preserve.

@NicolasDenoyelle @Kerilk @iskra-anl what's your opinion on deleting old benchmarking work from this repository ?

@NicolasDenoyelle
Copy link
Author

I will not be missing these branches. You can go ahead and remove these branches.

I would add the following branch in the delete batch:

  • dma_cleanup: We did not end up approving the changes and they were not critical. As the master branches moves forward, it is getting harder to use this work than redoing it from scratch.

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