Skip to content

Conversation

jwerle
Copy link
Member

@jwerle jwerle commented Aug 7, 2014

No description provided.

@jwerle
Copy link
Member Author

jwerle commented Aug 7, 2014

cc @willemt @stephenmathieson

@jonathanmarvens
Copy link
Member

@jwerle

How hard would it be to contribute changes back upstream? If it's possible, I think it'd be better than making the changes here, unless we've decided to actually maintain a version of libcoro here.

What do y'all think?

- Jonathan

@willemt @stephenmathieson

@jwerle
Copy link
Member Author

jwerle commented Aug 7, 2014

Not hard at all if that is what we want to do :]

On Thu, Aug 7, 2014 at 1:23 PM, Jonathan Barronville <
[email protected]> wrote:

@jwerle https://github.com/jwerle

How hard would it be to contribute changes back upstream
http://software.schmorp.de/pkg/libcoro.html? If it's possible, I think
it'd be better than making the changes here, unless we've decided to
actually maintain a version of libcoro here.

What do y'all think?

  • Jonathan

@willemt https://github.com/willemt @stephenmathieson
https://github.com/stephenmathieson


Reply to this email directly or view it on GitHub
#1 (comment).

@stephenmathieson
Copy link
Member

lgtm and yeah if think any bug fixes here should definitely end up upstream

edit: it's cvs? fuck yeah.

@willemt willemt self-assigned this Sep 23, 2016
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

Successfully merging this pull request may close these issues.

4 participants