Skip to content

Move non-sweap binaries/code/data to its own branch #1

Description

@lou1306

As the title says. Currently the main branch contains:

  • Competing synthesis tools
  • Related additional software dependencies (binaries, libraries, etc.)
  • Related benchmarks for these tools
  • Additional code (e.g., benchmarks/scripts) used to compare Sweap to these tools

I feel like these things should go into their own branch, it would lighten up main and it makes it easier for us to track commits related to actual code vs those related to benchmarking/evaluation.

Of course we should also maintain some discipline and NOT commit Sweap code to such a branch. It should only receive downstream changes from main (or possibly some other development branch).

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions