copilot-bluespec: Include in mainline copilot repo. Refs #623.
#625
Conversation
RyanGlScott
force-pushed
the
develop-copilot-bluespec-upstream
branch
4 times, most recently
from
0811114 to
3728d59
Compare
|
Change Manager: The README under copilot-bluespec and the cabal file are not the same. I can understand the difference in the Cabal file but not the one in the the README. Can we have one commit that just adds I prefer to leave the change to the cabal file and the README for a separate issue. Let's try to keep this as simple as possible. There has to be a commit in the history of |
…uage#623. The `copilot-bluespec` package was originally developed in an external repo (https://github.com/Copilot-Language/copilot-bluespec), but there is interest in having all Copilot projects and libraries merged into the main https://github.com/Copilot-Language/copilot repo for ease of management. This commit includes the last state of the old `copilot-bluespec` repo into the main Copilot repo as a new subdirectory, disregarding the commit history. It also adjusts the `copilot-bluespec` changelog to make the old issues refer to `copilot-bluespec#<ISSUE_NUM>` so that they are not interpreted as related to the main repo.
…guage#625. The `copilot-bluespec` package was originally developed in an external repo (https://github.com/Copilot-Language/copilot-bluespec), but there is interest in having all Copilot projects and libraries merged into the main https://github.com/Copilot-Language/copilot repo for ease of management. Now that the `copilot-bluespec` package lives in the `copilot` repo, this adjusts the issue numbers in the `copilot-bluespec` changelog to refer to the old repo so that they will not be confused with issues in the `copilot` repo.
RyanGlScott
force-pushed
the
develop-copilot-bluespec-upstream
branch
from
3728d59 to
d3ea6cd
Compare
|
I have reverted the changes to the README and |
|
Implementor: Fix implemented, review requested. |
The
copilot-bluespecpackage was originally developed in an external repo (https://github.com/Copilot-Language/copilot-bluespec), but there is interest in having all Copilot projects and libraries merged into the main https://github.com/Copilot-Language/copilot repo for ease of management.This commit includes the last state of the old
copilot-bluespecrepo into the main Copilot repo as a new subdirectory, disregarding the commit history. It also adjusts thecopilot-bluespecchangelog to make the old issues refer tocopilot-bluespec#<ISSUE_NUM>so that they are not interpreted as related to the main repo.Fixes #623.