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.

Sign up for GitHub

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

Jump to bottom

Branch: symbiflow-badger #80

Open
4 tasks
acomodi opened this issue Jun 7, 2019 · 0 comments
Open
4 tasks

Branch: symbiflow-badger #80

acomodi opened this issue Jun 7, 2019 · 0 comments
Labels
local-change Local change branch that does not need to be sent upstream

Comments

@acomodi
Copy link
Collaborator

acomodi commented Jun 7, 2019 •
edited
Loading

Why did we need this? (what does this change enable us to do)

This patch enables SymbiFlow/VTR README.md to use the SymbiFlow build badger

What did it change?

Change the VtR badge in the README.md

Should it be merged upstream - if not, when can we delete it?

No, there is no need to delete this branch. It should be only kept locally.

What is needed to get this merged / deleted?

  • is the implementation work to make suitable for merging / deletion completed?
  • is there an associated test?
  • is this currently part of the Conda package?
  • is this properly cleaned up in our local repositories?

Tracker / branch / PR & other useful links

Comparison with master upstream VTR: verilog-to-routing/vtr-verilog-to-routing@master...SymbiFlow:symbiflow-badger
Branch: https://github.com/SymbiFlow/vtr-verilog-to-routing/tree/symbiflow-badger
@acomodi acomodi added the local-change Local change branch that does not need to be sent upstream label Sep 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
local-change Local change branch that does not need to be sent upstream
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@acomodi